Brand colours and fonts live in config/theme.json, in the Astroplate / Sitepins format, so you can rebrand
from one file (or from Sitepins CMS):
{
"colors": {
"theme_color": { "primary": "#a7e2ff", "secondary": "#051a24", "accent": "#eafe63", "body": "#ffffff", "dark": "#061422", ... },
"text_color": { "text_dark": "#051a24", "text_muted": "#0d0d12" }
},
"fonts": {
"font_family": {
"heading": "Manrope:wght@400;500", "heading_type": "sans-serif",
"body": "Inter Tight:wght@400;500", "body_type": "sans-serif",
"accent": "Instrument Serif:wght@400", "accent_type": "serif"
}
}
}
utils/theme.tsreads the file at build time.layouts/layout.astrowrites the colours as--theme-*CSS variables, and the Tailwind tokens instyles/variable.css(--color-primary,--color-background-4, …) point to them, sobg-primary,text-secondary/60and the rest follow the file.- Fonts are Google Fonts loaded through Astro’s font API in
astro.config.ts: change a family name or its weights infont_familyand rebuild.headingdrives headings (font-manrope),bodythe body text (font-inter-tight),accentthe italic serif words (font-instrument-serif). - Components contain no brand hex values; add new colours to
theme.jsonandstyles/variable.cssrather than hard-coding them. .sitepins/config.jsontells Sitepins where content (data/), media (public/images/) and config (config/) live.