Examples
Inspect complete source specimens and their actual V2 reader output. Examples are file-based patterns, not subscription tiers, managed hosting or extra product features. Start with a small notebook, then add only the controls your workflow needs.
Choose a specimen
| Goal | Example |
|---|---|
| Inspect Markdown extensions | Markdown lab |
| Build a personal notebook | Small personal site |
| Organize team writing | Team handbook |
| Write an executable procedure | Runbook library |
| Assign operational ownership | Large organization |
| Separate reader audiences | Private and public outputs |
| Inspect the small scaffold | Starter download |
Practical recipes compares the patterns. Markdown lab puts input next to real rendered tasks, alerts, code, footnotes, tables and diagrams so you can inspect output rather than assume preview parity.
Use an example safely
Copy source into an isolated content tree and build into an expendable output folder. Keep private data and existing source outside that output. Inspect generated routes, links, headings, search, tables and diagrams before adapting the pattern to a live installation.
Replace synthetic names and prompts with reviewed content. Do not paste credentials into a specimen or mistake a read-only diagnostic for authorization to modify a service. The recipes describe expected results, limits and acceptance checks; they do not execute your infrastructure.
What the examples establish
| Evidence | Limit |
|---|---|
| Rendered Markdown | Not every imported dialect |
| Complete source specimen | Not a deployed service |
| Local task checks | Not production readiness |
| Governance pattern | Not built-in compliance |
| Separate output pattern | Not reader login inside V2 |
The starter archive is a five-file generic scaffold, not a full organization installation or offline runtime bundle. The personal-site recipe supplies a more complete worked task. External hosting, private-reader identity, TLS, service supervision and recovery remain your responsibilities.
Use Complete setup for the installation sequence, Use for writing controls and Run for operations. Validation limits states the scope of retained local evidence.