Tokens & branding
Nudova’s look is driven by design tokens — named values for colour, surface, and text that the storefront and admin both read. Change the tokens, change the look; you don’t touch component code.
The token layers
Section titled “The token layers”| Layer | What it controls | Where you change it |
|---|---|---|
| Accent | brand colour on buttons, links, highlights | tenant config token override ({"accent": "#…"}) or BRAND_ACCENT |
| Surfaces | backgrounds and glass panels | the theme preset |
| Text / semantic | body/heading text, success/warning/danger | the theme preset |
| Logo & name | wordmark and brand name | tenant config / BRAND_LOGO_URL, APP_NAME |
The default brand chrome follows Brand Guidelines v1.1 — warm canvas, Nudova Blue primary, magenta as a scarce accent. The reference accents:
| Token | Value | Use |
|---|---|---|
| Nudova Blue | #310DFA |
primary brand accent |
| Magenta (labelled) | #DB05A1 |
magenta surfaces that carry text |
| Canvas | #FBFAF8 |
page background (never pure white) |
| Ascend Mint | #34E5A4 |
growth signals only — rising numbers, positive deltas |
Runtime vs a themed build
Section titled “Runtime vs a themed build”- Runtime (no rebuild): accent colour, logo, brand name, preset choice,
feature flags. Edit the tenant config (or
.envfallbacks) and the storefront refreshes. - A themed build: a wholly new preset — new fonts, new layout. That’s a build, not a config edit.
See Theme presets for the presets you can pick, and Store settings & branding for where the values live.