Git Masterclass now has its skeleton. No lessons yet — deliberately. This post\nrecords what was built and why, because the reasoning matters more than the file\nlist.
\n\nFifteen modules, from orientation through internals to advanced topics, each with\nan overview page and sections for exercises and labs. A component library of\nsixteen MDX components. A content schema. Validation tooling. Contribution\nprocess, governance and automation.
\nWhat is not here is content, and that ordering is intentional. Conventions\ninvented while writing the fortieth lesson do not get applied to the first\nthirty-nine.
\nOrdering lives in the filesystem. Sidebar position comes from numeric\nfilename prefixes, and sidebars.ts names no individual document. A sidebar file\nthat lists documents is edited by every content pull request and becomes a\npermanent merge conflict — one that, resolved carelessly, silently reorders or\ndrops lessons.
Rules live in one file. content.config.json holds the module list, the\nfrontmatter schema, the tag vocabulary and the size budgets. The validation\nscripts read it, the generator reads it, and the authoring handbook documents it.\nWhen documentation and enforcement are separate copies of the same rule, they\ndrift, and contributors learn to ignore the documentation.
Validation runs without installing anything. The scripts under scripts/ use\nonly Node builtins, including a hand-written frontmatter parser. They run in a\npre-commit hook and in the first CI job, so a missing field is reported in\nseconds rather than after a five-minute build.
Staleness is dated. Every document carries last_reviewed, and a monthly\nworkflow turns overdue material into an assignable issue. This is the failure\nmode that actually kills teaching material: nothing about a stale lesson looks\nwrong, it just quietly stops being true.
The first module, written end to end. Every convention in the authoring handbook\nis a hypothesis until a real lesson tests it — and some of them will turn out to\nbe wrong.
\nIf you would like to write one, the authoring\nhandbook is the place to start, and lesson proposals go through\nthe issue tracker so that placement is agreed before anyone invests hours in\nprose.
", "url": "https://git-masterclass.nabenshrestha.com.np/updates/repository-foundations", "title": "Repository foundations", "summary": "The structure Git Masterclass will be written into — modules, components, conventions and the tooling that enforces them.", "date_modified": "2026-07-22T00:00:00.000Z", "author": { "name": "nabin747", "url": "https://github.com/nabin747" }, "tags": [ "Process", "Site" ] } ] }