This template uses Tailwind CSS v4 and DaisyUI v5 with themes: false. Brand look is not a stock DaisyUI theme name. Light and dark are site-light and site-dark, defined at the top of src/routes/layout.css (:root fonts, @theme tokens, OKLCH palettes).
What you actually change
| Layer | Where |
|---|---|
| Fonts | @fontsource imports at the top of layout.css (before Tailwind), full weights + latin-ext |
| Colour / radius | site-light / site-dark tokens in layout.css |
| Shape (preset) | Structural preset — Classic through Brutalist — via template code or /showcase |
| Colour set | Separate from preset (navy-gold, rose-teal, …) so you can mix a Brutalist frame with Rose & Teal |
| Components | Semantic classes (bg-base-100, btn-primary, .hero.pattern) — never raw hex in .svelte files |
The header theme toggle persists localStorage['theme'] and defaults to site-light.
Do not use stock DaisyUI theme lists
Older notes mentioned emerald, forest, cupcake, and dim. Those are not how this starter is themed. Adding themes: emerald --default in layout.css would fight site-light / site-dark.
Styling page bodies
Post and basic-page HTML (from markdown or the CMS rich-text editor) is wrapped in MarkdownBody. Headings, lists, quotes, and code blocks pick up shared prose styles. Prefer DaisyUI semantic colours so both themes stay readable.
Open /showcase to flip preset, colour set, fonts, header chrome, and button style without editing CSS. Template codes (TS… static, TA… Access, TC… CMS) bake those choices in when you create a parked site.