Contents
13 sections
- 01 Why a book Most LLM output is a wall. A book is a shape.
- 02 Where it came from A worked example: take real policy, lay it on a spectrum, let the reader find themselves.
- 03 The wager Walk an agent through what a book needs and the output comes back human-shaped.
- 04 The page Title. Hook. Body. Plain terms. Optional source. Always one screen.
- 05 The outline One file. One source of truth. Page numbers fall out of order.
- 06 The continuum Three formats: none, timeline, spectrum. Pick the axis the book lives on.
- 07 Rooms A book is more than its pages. The other rooms make the pages legible.
- 08 The runtime Small on purpose: gestures, md, palette, Giscus. Everything else is yours.
- 09 Cross-links Write
[[term]]anywhere in a body. It auto-links to the glossary. - 10 Gestures Wheel right, swipe left, press →. The same intent, three input devices.
- 11 Chapters and steps When the book is long enough to need internal structure, sections group into chapters and pages can alternate prose with code.
- 12 Static, deployable It is a SvelteKit site with adapter-static.
npm run build, drop the folder, done. - 13 Edit freely The scaffold is a starting point, not a contract. Routes are yours.