<?xml version="1.0" encoding="utf-8"?><?xml-stylesheet type="text/xsl" href="rss.xsl"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
    <channel>
        <title>Git Masterclass updates</title>
        <link>https://git-masterclass.nabenshrestha.com.np/updates</link>
        <description>New lessons, corrections and releases</description>
        <lastBuildDate>Wed, 22 Jul 2026 00:00:00 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>https://github.com/jpmonette/feed</generator>
        <language>en</language>
        <copyright>Copyright © 2026 Git Masterclass contributors. Content licensed CC BY-SA 4.0.</copyright>
        <item>
            <title><![CDATA[Repository foundations]]></title>
            <link>https://git-masterclass.nabenshrestha.com.np/updates/repository-foundations</link>
            <guid>https://git-masterclass.nabenshrestha.com.np/updates/repository-foundations</guid>
            <pubDate>Wed, 22 Jul 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[The structure Git Masterclass will be written into — modules, components, conventions and the tooling that enforces them.]]></description>
            <content:encoded><![CDATA[<p>Git Masterclass now has its skeleton. No lessons yet — deliberately. This post
records what was built and why, because the reasoning matters more than the file
list.</p>
<!-- -->
<h2 class="anchor anchorTargetStickyNavbar__nzj" id="what-is-here">What is here<a href="https://git-masterclass.nabenshrestha.com.np/updates/repository-foundations#what-is-here" class="hash-link" aria-label="Direct link to What is here" title="Direct link to What is here" translate="no">​</a></h2>
<p>Fifteen modules, from orientation through internals to advanced topics, each with
an overview page and sections for exercises and labs. A component library of
sixteen MDX components. A content schema. Validation tooling. Contribution
process, governance and automation.</p>
<p>What is <em>not</em> here is content, and that ordering is intentional. Conventions
invented while writing the fortieth lesson do not get applied to the first
thirty-nine.</p>
<h2 class="anchor anchorTargetStickyNavbar__nzj" id="the-decisions-worth-knowing-about">The decisions worth knowing about<a href="https://git-masterclass.nabenshrestha.com.np/updates/repository-foundations#the-decisions-worth-knowing-about" class="hash-link" aria-label="Direct link to The decisions worth knowing about" title="Direct link to The decisions worth knowing about" translate="no">​</a></h2>
<p><strong>Ordering lives in the filesystem.</strong> Sidebar position comes from numeric
filename prefixes, and <code>sidebars.ts</code> names no individual document. A sidebar file
that lists documents is edited by every content pull request and becomes a
permanent merge conflict — one that, resolved carelessly, silently reorders or
drops lessons.</p>
<p><strong>Rules live in one file.</strong> <code>content.config.json</code> holds the module list, the
frontmatter schema, the tag vocabulary and the size budgets. The validation
scripts read it, the generator reads it, and the authoring handbook documents it.
When documentation and enforcement are separate copies of the same rule, they
drift, and contributors learn to ignore the documentation.</p>
<p><strong>Validation runs without installing anything.</strong> The scripts under <code>scripts/</code> use
only Node builtins, including a hand-written frontmatter parser. They run in a
pre-commit hook and in the first CI job, so a missing field is reported in
seconds rather than after a five-minute build.</p>
<p><strong>Staleness is dated.</strong> Every document carries <code>last_reviewed</code>, and a monthly
workflow turns overdue material into an assignable issue. This is the failure
mode that actually kills teaching material: nothing about a stale lesson looks
wrong, it just quietly stops being true.</p>
<h2 class="anchor anchorTargetStickyNavbar__nzj" id="what-is-next">What is next<a href="https://git-masterclass.nabenshrestha.com.np/updates/repository-foundations#what-is-next" class="hash-link" aria-label="Direct link to What is next" title="Direct link to What is next" translate="no">​</a></h2>
<p>The first module, written end to end. Every convention in the authoring handbook
is a hypothesis until a real lesson tests it — and some of them will turn out to
be wrong.</p>
<p>If you would like to write one, the <a class="" href="https://git-masterclass.nabenshrestha.com.np/contributing">authoring
handbook</a> is the place to start, and lesson proposals go through
the issue tracker so that placement is agreed before anyone invests hours in
prose.</p>]]></content:encoded>
            <category>Process</category>
            <category>Site</category>
        </item>
    </channel>
</rss>