Code Coach Pack
Everything you need to run a project-based coding course — as a school semester or as a summer camp.
Pick your track
Both tracks teach the same material: every course in the hub is Intro + Setup + Stages 1-10. Only the pacing differs.
Semester track — 16 weeks (default)
One class a week, 60-90 minutes, for a school term.
- 16-week semester plan — week map, session shapes, the weekly rituals that make a once-a-week course work, absence and make-up policy, assessment, and substitute plans.
Camp track — 5 days
Three hours a day for a week, the summer-camp format.
- 5 days x 3 hours/day = 15 hours total.
- Day 5's last hour is the parent demo. That leaves 14 hours of working time.
- Day 1 — Setup, first build, first playtest
- Day 2 — Pick up pace and add more systems
- Day 3 — Build depth, test, and personalize
- Day 4 — Finish the core project and choose stretch work
- Day 5 — Polish, rehearse, and demo
The camp schedule is 2-3-3-2 + demo:
| Day | Focus | Why |
|---|---|---|
| 1 | Setup + first two build blocks | Soft start while students learn the tools |
| 2 | Three build blocks | Their hands are warm, so push pace |
| 3 | Three build blocks + personalization | Add depth and make projects feel owned |
| 4 | Final build blocks + stretch picks | Finish the core project and give choice |
| 5 | Polish + parent demo | Reserve the day for quality and celebration |
Shared pages
These apply to both tracks:
- Parent demo prep — room setup, student script, and day-of checklist
- Buffer activities — reusable activities for extra time or energy dips
Course-specific plans
Use the supplement for the course you are running. Each one carries that course's minimum viable finish, coach triage, and common stuck points — all of which apply to either track. Only their day-by-day tables are camp-specific.
Python Arcade, Scratch AI Lab, Python AI Assistant, Python 101, Python Machine Learning, Roblox Obby, Roblox Makers, Roblox Combat, Roblox Tycoon, Roblox VR Lab, Roblox YouTuber Studio, Bot Builders, Scratch App Studio, Scratch Game Studio, Geometry Dash, and Unity Castle Defense.
How to use each day page
Each Day N page in the camp track has:
- At a glance — a minute-by-minute table you can keep visible.
- Per-block notes — what to say, what to watch for, and when to move on.
- End-of-day reflection — a short prompt that helps students remember what they built.
The semester track uses one page instead of five, because the session shape repeats every week. See 16-week semester plan.
Before the first session
Both tracks:
- Make sure every machine can open the course tools and the Creator Hub site.
- Print this pack or keep it open on a second screen.
- Walk through Setup and the first build block yourself before students arrive.
- Decide whether the room will use a shared theme, individual themes, or free choice.
Semester track, additionally:
- Set up accounts that will still exist in Week 16 — school accounts, not throwaways.
- Decide where projects are saved between classes, and write it where students can read it all term.
- Give families the showcase date in Week 1, not Week 15.
Camp track, additionally:
- Email parents the format and demo time.
What to keep nearby
- The course page students are using on https://creatorshub.app.
- The stretch challenge sections for students who finish early.
- The Buffer activities page for short gaps, energy dips, or mixed pacing.