RUNBOOK
Add a page or prose to the site
How the authored-content layer works — add a Markdown file, and the site renders it fallback-first.
How it works
The site is a projection of atlas's generated data, with an authored editorial layer over it: site/content/**/*.md, parsed for light frontmatter and rendered through the shared Markdown pipeline. Pages read content when present and render their generated skeleton unchanged when it's absent — so nothing breaks for a missing file.
Steps
Add the Markdown file under
site/content/. The path is its id:site/content/systems/<name>.md→ the authored intro on/systems/<name>site/content/examples/<slug>.md→ a new example (see Add an example)site/content/home.md,vision.md,architecture.md,use.md→ those pages
Write light frontmatter, fenced by
---:--- title: ... summary: one sentence for cards and meta --- ## Start headings at level two The route renders the H1 title; the body starts at `##`.Link with root-relative paths only —
/systems/logos,/stack,/theory— never relative../links.Lint the seam:
node bin/atlas.mjs site lint --strict
Notes
- A content file must map to a known rendering surface, or
site lintflags it as an orphan. New top-level pages need their id added to the lint's known surfaces and a route undersite/src/routes/. - Frontmatter
systems: [a, b]entries must name real constellation members; the lint checks this.