For the Day 2 path owners. Goal: every path feels consistent and lands for ~10 mixed-skill attendees. Companion: 04 · Day 2 Path Outlines.
Your role
You own one Day 2 path end-to-end: the repo, the lesson plan, and running the room (~10 people) on Sep 9.
What to build
- Finished version first. Build the complete demo, then decompose it.
- Branch-chain repo from the
r3f-workshop-template: main (starter) → step-* checkpoints → final. Each step must compile and run on its own.
- A lesson plan using the template in the production tracker §6 (hook, objectives, libs, steps, pitfalls, stretch, done-check).
- 2–3 stretch goals for fast attendees; checkpoints for those who fall behind.
Standards (so all paths match)
- Keep new deps consistent with the template; commit the lockfile.
- README with screenshot/gif at top, run command, and the catch-up note.
- Same
pnpm step checkpoint UX as Day 1.
Timeline (anchored on Day 1 = Sep 8)
- By Jul 28: confirmed in; path + concept locked.
- Jul 28 → Aug 18: build finished version + branch chain + lesson plan.
- Aug 25 → Sep 1: dry-run your path end-to-end.
- Before travel (Sep 7): repo final, lockfile committed, screenshot/gif captured for the teaser + one-pager.
Path-specific make-or-break
- Editor: define the scene data model first — everything hangs off it.
- Car configurator: source the model early — licensing + clean material naming is the crux.