Claude Opus 5andbdeshi
91c733a0e0
notes-on-water had become a kitchen sink: every feature from the last eight loops on one page, which demonstrates the engine and misrepresents the site. Now each lands where a real site would put it. The text marks, the abbreviation, authored <kbd> and the margin note go to writing/typography, which is already the page about what the engine does to words. Icons and the grouped panels go to pages/colophon, which is the page about the theme — install instructions are what tabs are actually for. about gets a lone expando, the-flood gets a chapter note, and notes-on-water keeps what it is really for: the include and its namespaced footnotes, the gauge table, the glossary and a contents list over its own headings. Seven bundles carry features now instead of two, and the demo cases moved with them, so each still names the page it proves.
15 lines
668 B
Markdown
15 lines
668 B
Markdown
---
|
|
title: About This Demo
|
|
---
|
|
No date, so this page is not a feed item — the engine decides feed membership by asking whether something has
|
|
a publication date, which is a fact already on disk.
|
|
|
|
Every file under `examples/demo-site/` in the khosra repository is here to be *served* and read. If the engine
|
|
can do something this site does not show, that is a gap in the demo; if the demo asks for something the engine
|
|
cannot do, that is a gap in the engine.
|
|
|
|
:::details{summary="What is deliberately not shown"}
|
|
Anything the engine cannot do yet. The demo is a test as much as a brochure, so an empty section here would
|
|
be a failing case rather than a tidy page.
|
|
:::
|