Reference · the CMS engine
The editing machine
astro-inkstone is the paper; astro-inkbrush is the pen. The engine turns any Astro content site into its own editor: hover a paragraph in editing mode and a small handle offers ✎ edit, ✦ ask Claude, ⟲ history. There is no separate demo site to go look at — the garden you are reading is the demo. Run it with npm run wiki and every note here, this page included, opens for editing in place; a static build like the one you are reading contains not a single byte of CMS code.
- the only database
- git
- safety nets on every save
- 2
- CMS code in a static build
- 0 B
Five chapters
Revision history and revert
AI assist
The Obsidian inbox
How wikilinks resolve
Where it sits
The engine owns the CMS features and the Markdown dialect with its content guard — the grammar the editor accepts and the grammar the page renders must be one grammar, so it is written once and consumed everywhere (the three-way split explains why the line is drawn there). Styling belongs to the paper layer; identity belongs to your site. Everything rendered on these pages — the strip above this text included — is the paper at work; everything that edits these pages is the engine.
Reading path. New to the engine → Part I→Part II; wiring it into a site → the getting-started guide first; the dialect the save gate enforces → the kitchen sink; a note about keeping notes → the gardening essay.