Acceptance Criteria
- Each theme preset page follows one short template (pitch, opt-in snippet, palette, preview, attribution); "Composing with tideline" appears once, in
lumina.md; lumina.md no longer repeats the catalog's table and counts its presets correctly - The theme catalog's intro is written for someone choosing a theme
- Configuration migration lives in
migration.md, tint in its three audiences' pages linking each other, metaFields and friends in blocks-and-layout.md; the other copies link instead of repeating - Docs repeating a rune page (layout cascade, partial or include, rich menubar panels) link to it instead
- An Advanced group in the docs nav holds nav-slug-resolution, rich-menubar-panels, entities and entity-routes; theme tools move under extend;
extend/distributing/* is in the nav or removed; the contracts link in extend/index.md is fixed - One spelling throughout (
color, Internationalization)
Resolution
Completed: 2026-11-10
Branch: claude/composition-usage-rune-pages-c87ar6
What was done
- Nav: Advanced docs group (entities, entity-routes, nav-slug-resolution, rich-menubar-panels); theme CLI commands moved into
extend/theme-authoring/tooling.md, refrakt validate to docs/cli/validate.md, docs/cli/theme-tools redirects; extend/distributing/* in the extend nav; refrakt contracts link fixed. - Theme presets: one template on all nine pages; shared material in
lumina.md (nine presets, no repeated table); catalog intro rewritten for choosing a theme. - One home per topic: config migration (
migration.md), tint (concepts / rune / theme cascade, linking each other), metaFields family (blocks-and-layout.md); docs pages repeating layout, include and nav link to them. color and "Internationalization" throughout.
Notes
- Corrected on the way:
config migrate writes site.plugins; dark tint values are inline --tint-dark-*; metaRank no longer exists. config-api.md's Hint example still uses the deprecated structure field.