Showcase

Onboarding: a checklist that reads and tracks

Onboarding material decays fastest when it lives in three places: the checklist in a doc, the facts in a wiki, the quiz in a form. In one SemText document the procedure carries its statuses, the meter carries the score, and the facts double as flashcards — the same file the new contributor reads is the one a model can quiz them from.

The document

Render it and flip the flashcards: front is the statement, back the conclusion, and the incorrect statement on ob-main joins the quiz options when the deck is switched to quiz view.

onboarding.md

source

              
              <sem-enhanced-document>
            
                <h1 data-kind="title">First week</h1>
            
                <sem-progress value="0.4" label="checklist" role="meter" aria-valuemin="0" aria-valuemax="1" aria-valuenow="0.4"></sem-progress>
            
                <sem-procedure kind="checklist" role="list">
            
                  <sem-step role="listitem" status="done">Read the contributor guide</sem-step>
            
                  <sem-step role="listitem" status="done">Get repository access</sem-step>
            
                  <sem-step role="listitem" status="current">Ship a first change behind a feature branch</sem-step>
            
                  <sem-step role="listitem">Pair on a review</sem-step>
            
                  <sem-step role="listitem" status="blocked">Deploy shadowing — waits on the access audit</sem-step>
            
                </sem-procedure>
            
                <h2>Facts worth keeping</h2>
            
                <sem-facts view-as="flashcards">
            
                  <sem-fact id="ob-branch">
            
                    <statement>Where does feature work live?</statement>
            
                    <conclusion>In a worktree under .claude/worktrees/, forked from develop.</conclusion>
            
                  </sem-fact>
            
                  <sem-fact id="ob-main">
            
                    <statement>Who merges to main?</statement>
            
                    <conclusion>CI only — the release path is automated.</conclusion>
            
                    <incorrect-statement>The latest reviewer merges it by hand.</incorrect-statement>
            
                  </sem-fact>
            
                </sem-facts>
            
              </sem-enhanced-document>

render

Live render boots with JavaScript — the authored source is alongside.

Elements used: sem-progress, sem-procedure, sem-facts. Their contracts live on the reference pages .