stnd.buildSTANDARD MANUAL2026-07-15

stnd.build

stnd.build

The public face of the Standard. The concept — what Standard is — opens
packages/README.md; the norms themselves are the
bookshelf this site publishes at /manual. This app is the storefront that shows it.

The public home of the Standard (@stnd/*). Four jobs: the framework’s landing page (the living Standard::Design specimen), the bookshelf (the Standard::* norm books + the framework reference, fed live by the package READMEs), a live playground for testing components, and the fatal-error documentation — every fatal error in the framework logs a link to an explanation page here (the what / why / how).

Where it’s at — now

Active. The landing page shipped (July 2026): a 1970s graphic-standards-manual design (NASA/EPA style) — decimal sections, one federal-red seed color, Helvetica Now + Berkeley Mono — whose signature is that it documents itself live: every printed specification (type-scale sizes, color chips, ratios, the effective date) is measured from the running stylesheet via getComputedStyle, so the page cannot drift from the system it describes. Built on @stnd/* (core, lab, ui, icon, styles, modules…). Has a portfolio subfolder + sync-docs.js (bridges the manual).

What’s next — open

  • [x] Finish the landing page — the framework’s public face (the open-source front door).
  • [ ] Keep the error-doc pages in sync with the code (each fatal error → a /manual/<slug> page).
  • [ ] Manual Pages Audit Tasks
    • [ ] Review and publish private pages: Standard-VaultStandard-Daily-Noteapi-reference-vault-loaderhistory-and-decisions.
    • [ ] Expand stub pages: standardsvaultadvanced-patternscallouts.
  • [ ] Package READMEs Expansion
    • [ ] Expand thin package READMEs: @stnd/art@stnd/dom@stnd/lab@stnd/views@stnd/layout@stnd/loader@stnd/ai@stnd/client@stnd/server@stnd/cloudflare@stnd/icon@stnd/utils.
  • [ ] App Guides Integration
    • [ ] Integrate/publish guides for key apps: stnd.gd (Garden), stnd-obsidianreveal (Presentation engine), stnd-mac.

How it works — reference

Astro + Cloudflare. pnpm dev · pnpm test · pnpm build · pnpm deploy:prod. The test suite is a smoke layer that validates the manual content corpus and critical route files before deploy. The manual source lives in vault/Atelier/Kernel/Manual/sync-docs.js pulls it in. (Long-term: the package READMEs themselves become the manual’s source — see the packages/ discussion.)