Zone Home
0

Why Your Website Style Guide Didn’t Stop the Drift

We worked with a university on retainer for about three years, and shortly after we started they sent over a new brand style guide that looked ten times better than anything they’d had before. We designed new building blocks for their website straight from it. A few years in, they started telling us some of their new pages didn’t look on brand, and when we went looking, a few folks on their team had been building those pages out of blocks from the archive….. blocks that were five-plus years old and only still in the library so their older pages (on a site with 3,000+ of them) kept working.

The style guide was fine, but when a staff member needed a page, the old block was the easiest thing to pull in, so that’s what got used.

I call what happened there “design drift,” and in plain terms it’s the slow way a website stops looking like one company as different people edit it over 12 to 24 months, one good enough page at a time. A style guide on its own won’t stop it, because at the end of the day, we’re all human, and we go for whatever is (a) easiest or (b) will make our boss happy with the end result.

A website style guide is the set of rules that keeps every page on your site looking like the same company. It only stops drift when those rules are built into the editor your team works in, because a style guide that’s harder to use than improvising will lose to improvising every time.

What is a website style guide?

A website style guide is the rulebook for how your site looks: which fonts go where, how big a heading is, what a button looks like, and which color means click this. Search “website style guide” and Google’s AI Overview gives you the standard list: logo rules, a color palette, typography, tone of voice, and imagery and icons. That list is correct, and if you’ve got a brand guide, it probably covers most of it already. Good. That work isn’t wasted.

What the list doesn’t tell you is where those rules should live and how to convert them to something your website can actually use. When you are building a landing page inside of WordPress (or any CMS) with a deadline, and the brand PDF is three clicks away….. We all know that copying something that exists and tweaking it to look unique will win.. So the useful question for a website style guide is whether the rules are built into the site in a usable fashion.

Why don’t style guides stop design drift?

Style guides fail because people take the easy path. We’re all human, and we design with whatever tools make our lives easier in the moment. If a design system isn’t built so that using it is the easy option, it doesn’t get used, and that’s true from web design all the way down to print design. You can have every template already built and somebody will still open Canva and make something willy-nilly.

You can have every template already built and somebody will still open Canva and make something willy-nilly

On a website it tends to play out like this. Your site launches and every button is green with rounded edges. Around month 3, someone adds a page and forgets to round the button edges (close enough, right?). By month 6, another team member needs a header, can’t find the header style, and just makes the text bigger by hand. By month 12 half your buttons look different, and somewhere around month 24 someone finally breaks and says the words “we need a redesign.”

Every one of those people was trying to make the page better, and making the text bigger by hand was one click away while the header style was sitting in a document somewhere. That’s why (for sites that are actively used) typically land in a 2-to-3-year redesign cycle, and why I’d call drift an operations problem before I’d call it a design one. (If you’re pricing one of those out right now, here’s what a website redesign costs).

A marketing manager on Reddit said:

“I want my team (none of them code) to be able to ship copy and new sections themselves, on brand, without the ability to nuke the live site.”

The part about being “on-brand” has to be built into the site itself, because nobody stops a page build halfway through to go read a PDF.

What should a website style guide include?

A website style guide should cover every element someone touches when they build a page: headings, paragraph text, font sizes, buttons, the color palette, image treatment, and the blocks your pages are made of. For each one it should also say where that rule lives on the site, and the best answer is “it’s already built in.”

PieceWhat it coversWhere it should live
Headings (H1 to H6)Font family, size and styling for every heading levelLocked in the theme, so an H2 looks like every other H2
Paragraphs and bulleted listsBody copy stylingStock styling that looks the same wherever it’s dropped
Font sizesThe handful of sizes your brand usesA dropdown of named sizes (small, large, extra large), no pixel values
ButtonsShape, color, corner roundingA few pre-designed button styles to pick from
Color paletteBrand colors, and which one means “take an action”The theme’s color palette, with one call-to-action color
ImageryPhoto style, crops, shapesInside the block design, so it isn’t left to whoever’s editing
Blocks (page sections)Every section type your pages are built fromA block library page: each block named, described, and shown in use

On the sites we build, the top four rows are locked exactly like that. All the headers, 1 through 6, have an exact font family, font size and styling. Paragraphs have stock styling and look the same wherever you put them. Font sizes have names: if you want a paragraph bigger, you choose large or extra large from the dropdown and never think about pixels. And buttons come pre-designed in three styles: solid, outline, or plain text with nothing around it. When each of those micro elements has a locked-in style, the person building the page doesn’t have to think about any of it, and the easier it is, the easier it’s going to be for people to maintain their website long term.

Color deserves one extra rule: pick the one color that means take an action and don’t use it on anything else. I see this a lot on monochromatic sites. Everything’s white, blue and light gray, so every time somebody wants something to stand out they make it blue, and when every accent is blue, nothing stands out. We’ve been designing for a client with about five product lines, each aimed at a pretty different customer (one very hardware oriented, one very beachy, one very mountains). On their existing site, each product’s landing page has its own font. On the new one, the imagery, the iconography and even the base color can shift a little from product to product, but orange is the call-to-action color on every page.

Small stuff counts too. Button sizing, how rounded the corners are, whether images get cut into shapes or sit as plain squares….. those are the details that let you tell which pages were built by the professionals and which were built by an admin.

What does a style guide built into the website look like?

It looks like a block library: one page on your site with every building block laid out, named, described, and showing how to use it. A block is a section of a page, like a two-column text-and-image section or a row of icons, and on our builds they come in two types. Some are fully custom, with swooshes, overlays or patterns you’d never want to recreate from scratch. Others are flexible WordPress (Gutenberg) drag-and-drop blocks with images and text you fully control, and a handful mix the two.

If you want to see one, we keep a sample block library on our own site with real blocks laid out the way a client’s would be.

The trick is making the blocks flexible enough that people don’t feel boxed in. For the university, we designed a two-column block that could run image-left or image-right, and an icon section that could be one, two, three or four columns depending on what the page needed. The goal is that it’s harder to build willy-nilly from a blank screen than it is to go to the block library, grab a handful of blocks, and start from there.

It also means we build with intentionally fewer blocks than most sites have. When we cataloged one client’s existing site, we found 40 to 45 different blocks, including four different versions of a card with an icon at the top that all did the same job and all looked different from one another. Their overall look is pretty good, so there’s no full redesign; they’ll end up with a library of about 15 to 16 blocks, each with a couple of layout and color options. That’s a style guide somebody can hold in their head. (And it’s yours: if you ever stop working with us, the block library goes with you. More on that in no lock-in web design and how to let a marketing team edit the site without breaking it).

How do you get a team to use the style guide?

You make using it the path of least resistance, and then you teach it. Right before or right after launch, we host a live training session for about an hour so people can see the site, poke around, and ask their gut-reaction questions. Then we send over a library of training videos:

That combination should get a team to 90% to 95%. I’d never say 100%, because there’s always something missing. The point is that someone who hasn’t touched the site in a while can find the exact block they need and get a reminder of how it works, since the muscle memory of editing a page fades fast when you only do it every few months.

The other half is a habit for building pages that keeps anyone from starting at a white screen. I wrote that up step by step in the order of operations that keeps a new page on brand.

One honest tradeoff: every bit of flexibility you give people is a little more room to drift. You could remove all the optionality and make page-building a form to fill out, but then people want more flexibility. So the job is purposefully choosing where that flexibility goes.

When is it okay to break the style guide?

When you have a reason you could explain to your team in one sentence. I’m not opposed to trying something new at all, especially if it falls within the brand’s guidelines: go for it, try it out, add it to the library, and if it works, let’s go. The problem is the new idea that goes against the brand standards just to be a little cutesy. Without an intentional reason to be way different, it’s just noise.

I break my own site on purpose, for the record. Now, the website is a full-fledged video game. But at the beginning, I only dropped a retro-style banner section for the homepage. Nothing else on the site matched, and I ended up poking some fun at it and called it a “glitch” further down the page. That’s intentional, and I wrote about why I’m breaking my own website if you want the reasoning. The line between that and drift is intention, and I get into it more in healthy evolution versus drift.

A 5-minute check you can run today

Open any page on your site in the editor and try these:

  1. Drop in a paragraph. Can you type in any pixel size you want?
  2. Add a button. Can you pick any color from a color wheel?
  3. Is there ONE page (hidden from Google) where you can see every block your site uses?
  4. Scroll a few pages. Can you tell which ones your web team built and which ones an admin built?

(Want a second opinion? Take the drift quiz.)

If the first two came back yes, your style guide is a suggestion, and it will lose when there is a deadline in place. The good news is that fixing it usually doesn’t mean starting over. Most of the time it means consolidating the blocks you already have and locking the small stuff, so your team can open the site on a Tuesday afternoon, build a page, and hit save without wondering if it looks right (or waiting on a developer).

If that sounds like your site, book a call with us and we’ll look at it with you. And if you’d rather hand the small page work to us for a while, that’s what our care plans are for.

FAQ

Is a website style guide the same as a brand style guide?

Not quite. A brand style guide covers your brand everywhere, from print to social. A website style guide is the piece of it that has to live inside the site: heading levels, named font sizes, button styles, the call-to-action color, and the block library. Keep the brand guide as the source and let the website carry the rules.

How many blocks should a website have?

Fewer than most sites end up with. One client we cataloged had 40 to 45 different blocks, several doing the same job, and they’ll end up with about 15 to 16, each with a couple of layout and color options.

Does this work on Webflow, Squarespace or Wix?

Yes, and no platform stops drift on its own. Every CMS is powerful enough to let someone change font colors and sizes, so you can drift a site no matter how locked down it is. The names change too: WordPress’s Gutenberg calls saved sections patterns, and other platforms call them components, building blocks, layouts or templates.

Where should the block library live?

On your website. Create a page called block library, make it unindexable by Google if you can, and save each pattern there with a name. If your CMS lets you save that pattern in the backend too, give it the exact same name so people can drop it onto a page without hunting for it.

Who should own the website style guide?

One person. In a small company that’s a gatekeeper who makes sure the brand, messaging and design rules are followed, and who also knows when it’s a good time to break them on purpose. I cover that in more detail in who should edit your company website.

Ready to chat? Let's plan your next website. Grab 30 minutes with Chris LaFay of Classic City.

    Want to dive deep into your site? I’d love to chat.