Teacher guide

Quick start (first week)

1. Create your teacher account and verify email.
2. Spin up a section per period-note the join code on your syllabus slide.
3. Start everyone on the same first lesson so peer debugging norms stick (HTML intro works well).
4. Reserve five minutes for class norms: browsers allowed, headphones optional, AI assistants policy per district rules.

Sections & rosters

Each section maps to one cohort of students. Use distinct sections when pacing differs-even if you teach the same course twice in a day. Rosters aggregate across sections from your dashboard when you need a district-wide export for reconciliation (CSV).

Join codes regenerate security-wise only when you archive inactive sections; rotating codes mid-semester strands confused families-avoid unless compromised.

Choosing a pathway

• Coding track:HTML/CSS → JS → Python through APCSP and APCSA — ideal for standalone CS or technology rotations.
• Prompt Engineering track:a four-module path through LLM foundations, core prompting techniques, structured output and tool use, and reliability for production — great as an AI-literacy elective alongside any track.
• Entrepreneurship track:a full school year of team projects, guest speakers, and build-and-pitch milestones — pairs naturally with business electives.
• Finance track:personal finance modules feeding into the market simulator and a thesis-style written pitch — a strong capstone for interdisciplinary cohorts.

Mixed cohort? Alternate weeks between coding studios and project work but keep assignments anchored so grading stays manageable — students crave predictable rhythms.

Assignments & gradebook

Publish assignments when instructions are final-students only earn predictable UX once publishing flags align with your pacing calendar. The gradebook stitches submissions across assignments per section; blank cells usually mean no submission row yet (student hasn't opened task) rather than a zero.

Talking with families & admins

Lead with what students ship: Git-ready snippets, canvas screenshots, pitch recordings. Families understand portfolios faster than rubric jargon. When procurement asks about privacy, point them to our Privacy Policy, PIPEDA overview, and your district's data-processing agreement template-we'll complete vendor questionnaires on request.