Blog
5 min read
Turning Homeschool Coaching Into a Bookable Product: International School of America
Jun 12, 2026
Brand consistency sounds like something you buy from an agency — a thick PDF, a logo lockup, the phrase "visual identity." Strip the ceremony and what's left is small enough for any business: a handful of decisions, given names, stored where everything inherits them. That's a design system. The PDF version gathers dust; the working version is the reason your fourth service page looks like your first.
Quick answer: Pick a small palette (one primary, one accent, working neutrals), two type families with a fixed size scale, and store them as named site design styles — "heading color," not a hex code pasted forty times. Every page inherits the decisions, AI builds inside them, and the same named choices flow into your social templates and email designs. Rebrand later by retuning the names, not repainting the pages.
A design system is decisions with names
The difference between a brand and a vibe is whether the decisions have names. "Our headings are #111827" pasted into forty pages is a vibe — forty copies of a choice, each free to drift. "Heading color," defined once in your site design styles and referenced everywhere, is a decision: it has one home, one value, and one switch to flip when it changes. Designers call these tokens, but the idea needs no jargon — it's a label on a paint can, so nobody ever eyeballs a match again.
If this sounds familiar, it should: it's the voice guide, visual edition. Same disease (each page answering the same question slightly differently), same cure (move the decision out of the moment and into an artifact), same two readers — your team and your AI. A page built by describing it inherits the tokens automatically, which is precisely what makes AI page-building safe: its degrees of freedom are your content, never your colors.
The palette: fewer decisions, working harder
Small-business palettes fail by addition — every campaign donates a new blue until the site has nine. The working set is five or six named jobs:
| Token | Job | Discipline |
|---|---|---|
| Primary | Your brand's color — the one customers would name | Used confidently, not everywhere |
| Accent | Action: buttons, links, the thing to click | If everything is accented, nothing is |
| Text + headings | Reading, 95% of every page | Dark enough to pass the squint test forever |
| Backgrounds | The quiet majority: page, panels, cards | Neutrals, two or three steps |
| Functional | Success, warning, error | Conventional (green/amber/red) — don't brand the alarm |
The accessibility win hides in the structure: check contrast once, at the token level — text-on-background, accent-on-background — and every current and future page passes by inheritance. That's the difference between auditing forty pages and auditing five pairs.
Type: two families, sizes from a menu
Typography needs two decisions, then a menu. The decisions: a heading family with personality and a body family built for paragraphs (one family doing both is fine; four families is a ransom note). The menu: a short, fixed scale of sizes — headline, section, subsection, body, small — chosen once, so no page ever invents "a bit bigger than body" again. Size-from-a-menu is also what keeps your heading structure honest: when h2 always looks one way, nobody fakes a heading with bolded big text, and the outline machines read stays true.
One brand, every surface
The same five paint cans should color everything a customer sees, because recognition compounds across surfaces:
- The site inherits tokens by construction — pages, templates and sections, all drinking from the same cans, with the theme editor as the room where the cans live.
- Social gets the same decisions baked into your Design Studio templates — the slide that's recognizably yours before a word is read is just your tokens, traveling.
- Email carries them through reusable templates, so the newsletter looks like the site that looks like the carousel.
- Assets have one home: the current logo, in its approved variants, in the media library — referenced, never re-uploaded. Six slightly different logos in circulation is the asset version of nine blues.
A customer who sees your carousel Tuesday, your newsletter Thursday, and your booking page Friday should experience one business three times — not three cousins.
Evolving without churn
The system's last gift is how it changes. A freshen-up — warmer accent, softer backgrounds — is a retune of the named values, propagating everywhere at once, rather than a six-week repaint of every page. (Bigger restructures ride the branch-and-redirect rails; a token retune doesn't even move a URL.) Three habits keep evolution sane:
- Change tokens, not pages. If a page needs a special color, the question is never "what hex?" — it's "which existing token does this job, or does the system genuinely need a new one?" The second answer should be rare; that gate is the system staying small enough to stay used, same as minting templates.
- Write the why next to the what. One line per token — "accent: teal, chosen against the photography" — turns next year's "why is this teal?" from archaeology into reading. The two-page voice guide has room for it; one brand document, verbal and visual halves.
- Rebrand on purpose or not at all. The system makes change cheap, which is its own small hazard — retuning quarterly because you can burns the recognition you've compounded. Brands appreciate by holding still; spend the change budget when the business actually changed.
Key takeaways
- A design system is decisions with names: "heading color" defined once beats a hex code pasted forty times — one home, one value, one switch when it changes.
- It's the voice guide, visual edition: same drift disease, same artifact cure, same two readers — your team and your AI, whose degrees of freedom become content, never colors.
- Five or six color jobs, two type families, sizes from a menu: palettes fail by addition, and "a bit bigger than body" should not be inventable.
- Check contrast at the token level: five pairs audited once, every page passing by inheritance — accessibility as a structural property.
- Tokens travel: the same decisions color the site, the social templates, and the email designs — one business three times, not three cousins.
- Evolve by retuning, rarely: change the named values and everything follows — but brands appreciate by holding still, so spend change when the business changed.
Frequently asked questions
I'm not a designer — how do I pick the actual colors?
Steal from yourself first: your logo, your storefront, your product photos already contain a palette — pull the dominant color as primary and pick an accent that contrasts with it. Then run the two checks that matter: the accent must be obviously clickable against your backgrounds, and text-on-background must pass the squint test. Beyond that, restraint outperforms inspiration — a modest palette used consistently reads as more professional than a brilliant one used loosely.
What if my logo's color fails the contrast checks as text?
Common and fine: the logo color becomes your primary — used for brand moments, fills, and graphics — while a darker cousin of it (or plain dark neutral) becomes the text token. Brand color and reading color are different jobs, and forcing one can to do both is how sites end up with pale headings nobody can read outdoors. The logo doesn't change; the system just refuses to make it do work it's bad at.
How is this different from just using my theme's defaults?
Defaults are someone else's decisions — perfectly serviceable, and shared with every other site on the same theme. The system is the thin layer that makes them yours: your palette in the named slots, your type pairing, your scale. The mechanics are identical either way; the difference is whether the fourth customer touchpoint this week deepened recognition of your business or of a template. An afternoon in the design styles buys the difference.
Should seasonal campaigns get their own colors?
Give campaigns a lane, not the keys: the holiday promotion can carry a seasonal flourish in its imagery and its hero section, while buttons, text, and structure stay on-system. That way the campaign reads as your business, dressed for the season rather than a different shop. If every campaign demands new structural colors, that's usually the accent token being too timid — fix the system once instead of escaping it quarterly.
Ready to name your decisions? Faster keeps the cans in one place — site design styles every page inherits, social and email templates that carry them, and AI that builds inside your system instead of around it. Start free and pull your palette from your own logo tonight.