Service footprint
Starter template for brand-led service sites
Launch the next site from a stronger default.
This starter gives new projects a clear structure, stronger metadata, better hosting defaults, and a homepage that already feels intentional.
For new brands
From day one
Structure
Site config is separate from page composition.
New projects should not bury domain settings, brand details, and nav labels inside large layout files.
Metadata
The document shell already knows how to behave.
Canonicals, social tags, schema hooks, Matomo, and basic brand metadata all ship from the start.
Operations
Hosting defaults are part of the starter, not an afterthought.
Security headers, caching, and host canonicalization should be standardized before the first content sprint.
How to use this
Start by changing the brand, not the architecture.
The fastest way to ship more consistent sites is to lock down the technical seams and leave the visible brand system flexible. That means strong defaults for metadata, analytics wiring, content structure, and security headers, with enough room to give each site its own tone, typography, imagery, and page composition.