Acceptance Criteria
refrakt.config.json adds "presets": ["@refrakt-md/lumina/presets/niwaki"] under sites.main (or whichever site is current)- A visible signal of which preset the site uses exists — author's choice between three options (capture in resolution):
- A small "Theme: base + niwaki" indicator in the docs sidebar footer
- A line in the site footer like "This site uses Lumina's neutral default with the
niwaki syntax preset" - A deliberate mention on the homepage explaining the composition with a link to the preset docs
- After change: every code block on the site renders with niwaki colours; all other content (callouts, headings, body, surface) renders with neutral default
- A user clicking through marketing → docs sees no preset change — niwaki applies site-wide
cd site && npm run dev boots cleanly; no console warnings; code blocks visibly use the Japanese-garden palette
Approach
This is a one-line config edit plus a signal-component decision.
For the signal: the lightest option is a small text indicator in the footer. The most discoverable option is a homepage mention. Decide based on what feels right when you see the site rendered — capture the choice in the resolution.
Consider deferring the signal to the preset docs pages (WORK-208) — those pages exist specifically to surface the architecture, so a sidebar link "See how this site is composed" from any docs page might be enough on its own. Worth a brief read of how Vercel and Linear signal their own theme choices for reference.
Dependencies
- WORK-205 — niwaki preset must exist.
- WORK-200, WORK-201, WORK-202 — neutral default fully populated.
References
- SPEC-051 — "Site & Scaffold Implications" section explains the dogfooding rationale
refrakt.config.json — file being edited