The brand colours and the font live in one file, src/config/theme.json. Change a value, save, and the whole site
follows. With Sitepins CMS the same file shows up as a form, so colours and fonts can be
changed without opening the code.
{
"colors": {
"theme_color": {
"primary": "#0c388d",
"secondary": "#082a6e",
"accent": "#9fb2d8",
"body": "#ffffff",
"light": "#f6f6f6",
"surface": "#e6e5dd",
"border": "#dcdbd7"
},
"text_color": { "text": "#6f6c67", "text_dark": "#252320" }
},
"fonts": {
"font_family": {
"primary": "Geist:wght@100..900",
"primary_type": "sans-serif"
}
}
}
| Key | What it changes |
|---|---|
theme_color.primary |
Brand blue: main buttons, featured plan, wordmark, accents, hover lines |
theme_color.secondary |
Dark sections (process, call to action) and button hover |
theme_color.accent |
Light accent text on dark sections (footer, process, featured plan) |
theme_color.body |
Page background, and text on dark backgrounds |
theme_color.light |
Section backgrounds |
theme_color.surface |
Service preview panel |
theme_color.border |
Lines, borders and empty cells in the pixel counters |
text_color.text |
Secondary (muted) text |
text_color.text_dark |
Headings and body text |
font_family.primary |
The one font used across the site |
The font is any Google Fonts family, written as Family Name:wght@400;500 with the
weights you need, or Family Name:wght@100..900 for a variable font. It is downloaded and self-hosted at build
time. Pick a variable family and the range form if you want the footer wordmark to keep animating its weight; with
fixed weights it still works, just in steps. primary_type is the fallback (serif, sans-serif or monospace).
Colour changes show at once in pnpm dev; after changing the font, restart the dev server.
Lighter and darker steps (the button shadow tint, the line colour on the featured plan) are mixed from these colours
with color-mix() in src/styles/variable.css. Type sizes, easing and breakpoints are also set there, and the text
styles in src/styles/typography.css.