Colors and Fonts

Brand colours and fonts live in src/config/theme.json, using the same key names as Astroplate, so Sitepins CMS can edit them. Change a value there and the whole site follows: there is no generator to run.

Key Default Used for
colors.theme_color.primary #c9e86b lime accent: buttons, active tabs, highlights
colors.theme_color.secondary #031c14 deep forest: dark sections, overlays
colors.theme_color.accent #ddefde mint panels
colors.theme_color.body #fbfaf7 page background
colors.theme_color.light #ecebe4 sand cards and icon backgrounds
colors.theme_color.dark #111312 dark buttons and panels
colors.theme_color.dark_soft #232726 secondary dark surfaces
colors.theme_color.border #dcddd7 lines and borders
colors.text_color.text_dark #0b0d0d main text
colors.text_color.text_light #f5f4ef text on dark backgrounds, cream surfaces
colors.text_color.text_muted #626762 secondary text
colors.text_color.text_soft #8e928c placeholders and captions
fonts.font_family.heading Urbanist headings and display type
fonts.font_family.body Inter body text, labels, buttons
fonts.font_family.accent Italiana the serif accent words in headings

Fonts are written as Google Fonts names with weights, for example "Urbanist:wght@300;500;600", and each has a <role>_type (serif, sans-serif or monospace) used as the fallback. Astro’s font API downloads them from Google Fonts at build time and serves them from your own site.

How it is wired:

  • src/lib/utils/theme.ts reads theme.json.
  • src/layouts/base.astro writes the colours as --theme-* CSS variables and loads the fonts.
  • src/styles/variables.css points the Tailwind tokens (--color-lime, --color-forest, --color-ink …) at those variables; see-through variants use color-mix().
  • astro.config.mjs takes the font names and weights from theme.json.

Use the Tailwind tokens (bg-lime, text-ink, bg-forest/50 …) in components instead of hex values, so they follow theme.json too.

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