Technical HTML

You write Markdown. scripts/build.ts turns it into one .html file: no network, house CSS inlined, diagrams rendered with TALA and inlined as SVG. The page follows the reader's light or dark setting, and a small button at the top right switches it; that toggle is the only JavaScript in the page. The look lives in assets/style.css. Do not restyle it per document.

Files

• assets/examples/: one real document per type, as .md source and built .html. Copy the closest one; do not start from a blank page.
  • status.md: status report, roadmap or any living document. Stat cards, summary with a warning, status table with pills, roadmap steps, open decisions, risks.
  • design.md: design doc or explanation. Context, one diagram, trade-offs, with a table of contents.
  • how-to.md: how-to or runbook. Prerequisites, numbered step cards with commands, troubleshooting table.
  • reference.md: reference. Tables and code. It is also the full syntax reference for this skill: read it before you write.
• assets/house.d2: D2 variables and classes. The build adds it to every diagram, so diagrams never declare them.
• scripts/build.ts: the builder. Bun only, plus the d2 CLI with TALA.

Syntax in one screen

Full details and every build failure are in reference.md.