Can one design system run many brand sites?
Yes. Build one library of components, give each brand its own theme of colors, type and imagery, and let every site draw from the same library. Fixes and improvements land everywhere at once, new sites start from the system instead of from scratch, and brands stay distinct without separate codebases.
How it works
- Shared componentsHeroes, cards, forms and navigation are built once and tested once.
- A theme per brandColors, type, spacing and imagery are set as design tokens for each brand.
- A shared content modelThe same kinds of content are structured the same way on every site.
- A site templateA new brand site starts from a working template, not a blank page.
- Rules for allAgreed governance decides what’s shared and how brands ask for changes.
What stays shared, and what varies
- Shared: components, accessibility, performance, analytics and the publishing workflow.
- Varies by brand: colors, type, imagery, tone of voice and navigation.
- Sometimes varies: a few components only one brand needs.
Keeping it healthy
- A named owner who approves new components.
- A simple way for brands to request changes.
- Versions, so brands can adopt improvements on their own schedule.
- A component catalog that shows what exists and how to use it.
How Cypher handles this
The design systems and brand sites playbook builds one component library for every brand, a theme per brand with rules for all, and new sites from the system, not from scratch. Thirty brand sites on one design system. Yes, thirty.
Questions people ask
Won’t every site look the same?
Not if the themes are strong. Shared components can look very different with different colors, type, imagery and copy.
When doesn’t a shared system fit?
When brands need fundamentally different experiences, or run on different platforms that can’t share components.
How do we add a new brand?
Create its theme, set up a site from the template, and add its content. The components are already built and tested.