felix

I don't think I understand your question What second request? And what gets recompiled?

Normally you'd make every "entity" (instructors, (nationalitys,) courses, certificates) a template on it's own and create relations between them (ignoring the page tree setup - this is more of a personal preference). The tricky questions in this case are: - Are courses likely to be given several times by different instructors or is every course (like an event) only happening once? - Are the cards only related to the course (see question above) or also to the instructor? - Are there plans to add Countries / Languages in the future? I'd go with this setup if courses are "one time events": Instructors: - Instructor 1 - Single (Page-)Relation to Instructortype - Instructor 2 - Single (Page-)Relation to Instructortype [...] Courses - Course #1 - Multi (1:n) (Page-)Relation to Instructor - Course #2 - Multi (1:n) (Page-)Relation to Instructor [...] Cards - Certificate #1 - Single(?) (Page-)Relation to Course - Certificate #2 [...] Instructortypes - International - Italian Regarding the Cards: Just don't publish them until they're valid. After a course is finished (timestamp check) just delete all unpublished cards related to the course. Example code for this setup: // get all (valid) cards for course with ID "42" wire('pages')->find('template=card, course.id=42'); // get all instructors for italian courses wire('pages')->find('template=instructor, type.title=italian'); // get all courses from Instructor 1 wire('pages')->find('template=course, instructor.title=Instructor 1');

Count me in!

We're using a pretty opinionated yeoman generator somewhat similar (but different... i.e. no coffescript ) to the one from fixate. It's more or less like fireshell. The generator pulls a fresh copy of processwire + evergreen modules, sets up the directory structures, downloads npm & bower modules and creates basic templates + includes that we need for most of our projects. For the database part we're currently planig to integrate wireshell as soon as it leaves the beta status.

OnTopic: Stunning site and great designs. You're very talented. Great to have you here! On SPAs: We also did a "single page Website" with transitions recently (going to make a post on this somewhen in the near future). The transitions are based on a codrops experiment. For the URL-part we used History.js, every page is a "real" page but only renders it's content if it's loaded via ajax. This way even users without JS can view every page. I think this is the "cleanest" way to do "SPAs".

As promised here is the recipe: https://processwire-recipes.com/recipes/inline-critical-css/