The brand guidelines are a PDF. It has the logo, the clear space rules, the color values, two typefaces and a note about tone of voice. It was produced during the rebrand and it is genuinely good work.
It has never once prevented a problem. It also cannot stop anybody from building a page that looks nothing like your website, because it describes what the brand looks like rather than what the website is allowed to do. Those are different documents and only one of them holds a site together.
Where this sits. This is the practical companion to the argument that a website drifts one reasonable request at a time. That post named the component set as the first remedy. This one covers what a component set is and how to make it hold.
The Difference in One Sentence
A style guide describes appearance. A design system defines the finite set of things that can be built, and refuses the rest.
Everything else follows from the refusal. That refusal is the entire value. A style guide that says headings are set in Archivo Black permits an unlimited number of layouts using Archivo Black headings. A component set that contains eleven components permits eleven kinds of page section. The second one still looks like your organization after three years and forty contributors. The first one does not, and nobody can point to when it stopped.
What Is Actually in One
For an association website, a working component set is smaller than people expect. Most of what a site needs is covered by somewhere between ten and twenty pieces:
- Text and structure. Page header, section heading with optional intro, body text block, image with caption, pull quote, and the horizontal rule. Unglamorous, used constantly.
- Content display. A card grid for resources or programs, an event listing, a staff or board profile, a logo strip for sponsors, an accordion for questions. Each one pulls from structured content rather than being typed in by hand.
- Action. The primary call to action, the secondary one, the inline link, and a form embed. Four things. Most drifted sites have twenty variants of the first two.
- Membership specific. A member-only notice, a login prompt, and a restricted content teaser. Associations need these and generic design systems never include them, which is why they get improvised.
Keep it small on purpose. If your set has forty components, it is not a set, it is a catalogue, and nobody will read it before building a page.
Written Down Is Not the Same as Enforced
A component set that exists only in a document is a style guide with extra steps. What makes it hold is that the content management system will not let an editor do otherwise.
Enforcement is a technical property, not a policy. In practice that means the components exist as actual blocks or paragraph types in the CMS, with defined fields, and the page editor offers those and nothing else. No free-text HTML area. No page builder that permits arbitrary layout. An editor building a new program page picks from the list, fills in the fields, and produces something that matches every other program page because there was no mechanism available to produce anything different.
This is the difference between documentation and configuration. Documentation tells people the rule. Configuration means the rule does not depend on anybody reading the documentation, remembering it, or being available. Two of those three fail routinely.
The Exception Process Is the Hard Part
Real organizations need things their component set does not cover. A system with no route for that gets circumvented within a quarter, and circumvention is worse than no system because it happens quietly.
What a working exception process looks like. Somebody needs a page the components do not support. The request goes to whoever owns the system with one question attached: what happens if the next eleven people ask for this? Most requests do not survive that question, and the ones that do are genuine gaps. A genuine gap becomes a twelfth component, designed properly, added to the set, documented, and available to everybody. It does not become a one-off page.
The distinction is between an exception and a precedent. A campaign landing page that has to look different from the rest of the site is a legitimate exception. Make it a component called campaign landing page, with defined bounds, rather than a bespoke page. Then the second campaign uses it too, and the third, and you have a system instead of a precedent.
How to Build One From a Site You Already Have
Nobody starts from nothing. Most associations are retrofitting, and retrofitting has a sequence that works:
- Inventory what exists. Go through the templates and count the distinct button styles, heading treatments and section layouts actually in use. The number is usually between three and ten times what anyone expects, and the count itself makes the case to leadership better than any argument.
- Decide which survive. Of the nineteen button styles, two or three are doing real work and the rest are accidents. Pick the survivors deliberately rather than by which appears most often, because frequency often reflects one heavily copied mistake.
- Build the survivors as CMS components. The set only matters once it is the only option in the editor. This is development work and it is the step that gets cut when budget tightens, which is exactly how the site drifted in the first place.
- Migrate the old pages on a schedule you can live with. Not all at once. New pages use the system immediately, existing pages get converted when they are next edited anyway. A three-year-old page nobody visits can stay as it is.
What It Buys You
Three things, and the third is the one that pays for the work.
Editors stop making design decisions they were never meant to make, which is faster for them and safer for you. Pages become consistent without anybody policing consistency. And when you redesign, the content is portable, because it is structured content in defined components rather than markup embedded in a page, which is the single largest hidden cost in a re-platform.
Somebody Has to Own It
A component set with no owner degrades the same way the site did, only more slowly.
What the role requires. The owner does not need to be a designer. They need the authority to say no and enough standing that it holds, which usually means it sits with whoever runs the website rather than whoever runs marketing. The job itself is small: answer exception requests, add a component when a gap is genuine, and review the set once or twice a year against what has actually been built.
The failure mode is specific and predictable. If nobody owns it, the first urgent exception becomes the precedent, and you are counting button styles again in three years.
Count What You Have
Give us access to the site and we will produce the inventory: every distinct button, heading, and section layout in use across your templates, how many times each appears, which pages sit outside the system entirely, and which of your content types are structured rather than pasted markup. That count is usually the whole argument. From there we can tell you what a defensible component set for your site would contain and what it would take to enforce it in the CMS you already run.