Config-driven marketing sites — change the config, not the components

The slowest part of shipping a client site was never the code. It was the re-typing — the business name in forty files, the phone number in twelve, the brand color hard-coded into a button somewhere nobody could find.

So Forge sites are config-driven. Almost everything a business needs to rebrand lives in one typed file.

One source of truth

export const site = {
  name: "Northside Dental",
  tagline: "Gentle dentistry in Kitchener-Waterloo",
  email: "hello@northsidedental.ca",
  phone: "+1 (519) 555-0142",
  address: { city: "Kitchener", region: "ON", country: "CA" },
};

The components read from this. Change the name once and it updates the header, the footer, the page titles, the Open Graph tags, and the structured data — all at once.

The generic catalog model

A dentist has services. A dealership has vehicles. A venue has packages. Rather than build a bespoke schema for each, Forge ships one catalog model with a title, a summary, a category, a price, photos, and a flexible list of attributes. You map the business’s “things” onto that single model and the grid, search, and detail pages come for free.

Why this matters for maintenance

A small team can keep a config-driven site current because changing it doesn’t require reading the components. The owner edits content and config; the structure stays correct because it’s validated at build time. That’s the whole game: a site you can actually keep up to date.