Colors and Fonts

Brand colours and fonts live in one file, src/config/theme.json (the same key names as Themefisher’s Astroplate, so Sitepins can edit it). It is read at build time, no generator step:

Key Default Used for (Tailwind token)
colors.theme_color.primary #2d3622 olive: buttons, section cards, browser theme colour (olive)
colors.theme_color.secondary #201914 chocolate: footer, toasts, page transition (chocolate)
colors.theme_color.body #f1e6d8 cream page background and light text (light)
colors.theme_color.light #d7d1c3 sand card colour (sand)
colors.text_color.text_dark #000000 dark text (dark)
colors.text_color.text_light #ffffff white surfaces and text (white)
fonts.font_family.body Manrope:wght@400;500 headings and body text (font-sans)
fonts.font_family.label Geist Mono:wght@500 buttons, labels, tags (font-mono)
fonts.font_family.hand Gloria Hallelujah:wght@400 handwritten captions (font-hand)
fonts.font_family.footer League Spartan:wght@300 footer address and links (font-spartan)

Fonts are Google Fonts family names with their weights (Family:wght@400;500); each <role>_type is the fallback (serif, sans-serif, monospace or cursive).

How it is wired: src/lib/utils/theme.ts parses the file; src/layouts/Layout.astro loads the fonts from Google Fonts and writes the values as --theme-* CSS variables; the --color-* and --font-* tokens in src/styles/global.css point at those variables, and the in-between shades (cream-deep, cream-soft, chocolate-soft, khaki, scrim) are mixed from them with color-mix(). Opacity steps such as text-light/68 follow automatically, and so do <meta name="theme-color"> and site.webmanifest (built by src/pages/site.webmanifest.ts). Change a value, rebuild, and the whole site follows. Status colours (success, warning, error) stay in global.css.

Sitepins: .sitepins/config.json points the CMS at src/data, public/images and src/config; public/.well-known/sitepins.json marks the site as Sitepins-ready.

Improve this page on Github  — Last updated:  Wed, Nov 18, 2026