Teacher hub¶
You do not need to know Git before you start. Read the 3-hour training outline, then run Module 1 of Grade 8 from the printed guide.
Delivery tiers¶
| Tier | Setting | How lessons run |
|---|---|---|
| 0 | No computer | paper commits, Parsons cards, printed handouts |
| 1 | Offline computers | portable Git + VS Code from USB; practice repos as .bundle files |
| 2 | School LAN | Forgejo on a Raspberry Pi / old PC (see offline/README.md in the repo) |
| 3 | Internet | GitHub / Codeberg / GitLab; real open-source contribution |
Classroom practices¶
- Work in pairs (driver and navigator, swap every 10 minutes). This also covers "fewer computers than students".
- Read the commit history, not just the final file — it shows the student's process.
- Keep a no-shame progress chart: badges in each student's own
BADGES.md, never a public leaderboard. - Never put student names, photos or marks into a public repo (see
SECURITY.mdin the repo). - AI helpers: a student may use an AI helper only if they can explain every line of the diff they commit.
Assessment¶
Each grade offers a board-style written item bank (assessments/) and a practical rubric.
Start here¶
Read Part I. Teaching version control as a foundation: the concept spine, threshold concepts, misconception catalogue and assessment progression behind every lesson. Every lesson now has a full explanation, a worked example, a common-mistakes table, free-resource exercises and an answer key.