Customizing Your Site's Look
Version 1.2.0
Colors and a handful of layout values are real, editable data — change your palette by asking, and it shows up in the actual generated stylesheet at the next build. No CSS file ever needs touching.
What's actually editable
A fixed, known set of color and length tokens — not open-ended CSS. That's deliberate: a token name is meaningless without matching styles elsewhere already referencing it, and writing that part is Engineer/template work, not something this tier reaches. The current set:
| Token | Purpose |
|---|---|
color-bg | Page background |
color-text | Body text |
color-accent | Links and highlights |
callout-info / -warning / -danger / -success | The four callout variants |
content-width | Reading-column width |
gap-sm / -md / -lg | Spacing used by the layout primitives (stack, wrap, carousel) |
Light and dark, together
Every color takes a light and a dark value at once — there's no separate dark-mode system to configure. A visitor's own device preference decides which value renders; changing a token changes both modes in the same edit.
Changes are stored as the difference from the built-in defaults, not a full restatement of every value — so a one-color change produces a small, readable diff, not a wall of unrelated values.
What isn't here yet
Site-wide navigation (the top nav's links and labels) is real, editable data in the underlying system, but isn't currently exposed as a tool on this connector — that's a known gap, not a permanent limitation. Anything beyond colors, spacing, and content width — a new component, a new page template — is Engineer/template-tier work: real code, reviewed the normal way, not something this tier writes directly.