How-To Guides
This page collects task-oriented workflows for current 0x0 documentation and
site work.
Check Public Docs Safely
Use the bounded public docs gates:
make public-docs-milestone-0-check
make public-site-link-check
These checks inspect metadata and links. They do not invoke the legacy broad
docs gate.
Build The Static Site Locally
Use:
make public-site-build-check
The build writes generated files under build/site, which is ignored by git.
Add A Site Page
1. Add the Markdown file under site/.
2. Add or update the route in site/manifest.tsv.
3. Link the page from a relevant top-level page.
4. Run make public-site-link-check.
Add A Reference Page
1. Update the implementation doc under docs/.
2. Add a public link from Reference.
3. If the page is planned rather than current, mark the route as planned in
site/manifest.tsv.
Update Migration Docs
1. Keep jmp0x1b/lang claims separate from current 0x0 behavior.
2. Link historical context from Migration.
3. Put unsupported or embedded behavior under Embedded Status or
a deferred feature matrix.
Work With Libraries
For now, library registry work is represented by Libraries and
the package docs. Later milestones add registry metadata, alias policy, and
public package pages.
Avoid Unsafe Defaults
Do not make make docs-check, broad compiler sweeps, parallel library
compilation, unbounded crawlers, or remote publish commands part of the default
public documentation workflow.