Colors and Fonts

The brand colours and fonts 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": "#ff5c34",
      "secondary": "#351e28",
      "accent": "#ff788d",
      "body": "#f7f3ea",
      "light": "#e9dfcf"
    },
    "text_color": { "text_dark": "#0a0608", "text_light": "#fffffc" }
  },
  "fonts": {
    "font_family": {
      "heading": "Instrument Serif:wght@400",
      "heading_type": "serif",
      "body": "Manrope:wght@400;500;600",
      "body_type": "sans-serif",
      "label": "Geist:wght@400;500",
      "label_type": "sans-serif"
    }
  }
}
Key What it changes
theme_color.primary Main buttons, links on hover, text selection, form errors
theme_color.secondary Dark sections (call to action, testimonials, services dial), second button style
theme_color.accent Accent in the home story
theme_color.body Warm page background
theme_color.light Card surfaces (pricing, contact)
text_color.text_dark Text, borders and lines
text_color.text_light Text on dark backgrounds
font_family.heading Headings (keep a font that has an italic style; headings use italic words)
font_family.body Paragraphs
font_family.label Labels, navigation and buttons

Fonts are any Google Fonts family, written as Family Name:wght@400;500 with the weights you need. They are downloaded and self-hosted at build time. *_type is the fallback (serif, sans-serif or monospace). Colour changes show at once in pnpm dev; after changing a font, restart the dev server (a production build always picks it up).

Everything else (type sizes, spacing, shadows, easing, breakpoints) is in src/styles/variables.css, and the text styles in src/styles/typography.css.

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