BUILD// reference implementation
The project keeps the CloudCannon Astro Component Starter's page-section workflow and content-first routing.
The site swaps the demo content for a narrative archive, keeps editing focused in Markdown and YAML, and uses native browser state instead of client-side puzzle code.
The build is designed to look copyable, not precious.
-
Three-file pattern
Every custom page section ships with an Astro file, an inputs file, and a structure-value file.
-
Editing stability
Pages compose from small sections, logs live in content collections, and metadata lives in YAML.
-
Performance as voice
No runtime logic drives the puzzle. The interface stays deterministic and crawlable.
Architecture choices
CloudCannon first
Page composition remains in src/content/pages, while reusable sections live in src/components/page-sections/terminal. Editors can rearrange the narrative surface without touching the structural components.
Zero-JS puzzle state
The directory explorer uses anchors and CSS state. The witness token uses native HTML validation plus :has() selectors. Unsupported browsers get a linear fallback instead of a broken puzzle.
Content collections that fail softly
Logs accept missing timestamps without breaking the build. When metadata disappears, the UI renders DATA CORRUPTED - TIMESTAMP UNKNOWN instead of throwing a fatal content error.
