custom theme
You absolutely can let customers “theme” this renderer—without breaking your current static-publish pipeline—by treating theme as data and layering it on top of your existing CSS variables, Fumadocs UI preset, and the scoped component system you already have.
Below is a pragmatic, staged menu of options (from “simple color picker” to “power-user CSS”) plus how each would plug into your current code paths (renderer + publish), what security constraints to enforce, and what JSON you’d ship to the renderer.
Some random content for deployment - api key mismatch causing trouble!
TL;DR — A layered theming model that fits your stack
Theme tokens (no‑code):
Expose a tiny set of CSS custom properties (your current:roottokens) as a site “Theme” object your web app saves at publish time. The renderer fetches that JSON and injects a