One Design System Has to Work on the Whole Website

In our September–October 2026 website work, we learned how easy it is for a site to look coherent on its busiest page and still feel like several different businesses elsewhere. A visitor may meet your brand on the homepage, then land on a pricing page, an article, a form, or a support screen. Every one of those pages is part of the same conversation.

The useful lesson is that a design system is a set of decisions you can carry through the whole journey. Colors and type matter, but so do button states, error messages, spacing, navigation, and what happens when someone chooses a light or dark view.

Make the rules visible first

We started with a clear reference for the Dash Digital site: an ink background, off-white text, IBM Plex type, blue actions, subtle grid details, and a working theme choice. Those choices gave us a way to judge another page. Without a reference, “make it consistent” can mean whatever the person editing the page happens to like that day.

For your business, the reference can be simpler. Write down the type styles, core colors, button treatment, spacing, and image approach that should repeat. Include examples of a form, a notice, and a page with a lot of text. Those are often where a polished homepage style begins to fall apart.

Follow a visitor, not a component list

Suppose someone reads an article, opens your services page, and clicks Contact. If the first page has a dark background and clear blue links, but the next page has a bright white card with faint gray text, the change feels accidental. If the contact button looks different again, the visitor has to stop and relearn what is clickable.

We checked the less-visible states, too: phone layouts, page bottoms, focus outlines, form feedback, and protected pages. A color rule that looks correct in code can still leave a label unreadable over a photograph or a button hard to read when hovered. The only convincing check is to look at those states after they render.

That does not mean flattening every page into the same template. A portfolio needs room for project imagery. A print view needs to work on paper. A warning should still look like a warning. Consistency means those exceptions are deliberate and still belong to the same family.

A theme choice has to travel with the person

A light or dark toggle is useful only if it keeps working after the next click. A visitor should not have to choose again on each page. That sounds obvious until a page loads in a different way, a component uses a fixed color, or an update changes how the page first appears.

Our October review checked both choices across different routes rather than judging the toggle by itself. This is a good model for any preference: test the journey after the choice, including the article, the form, and the return trip.

Where should a small team begin?

Pick a short path through the site. Start with the page people visit most, then follow the next two clicks. Note where type, color, navigation, or button meaning changes without a reason. Fix the shared rule when you can; use a page-specific exception only when the content truly needs one.

The objection is usually time: “We cannot redo every page.” You do not have to. A small, written set of rules and a repeatable review are easier to maintain than a one-time visual overhaul. Start with the most important journey and expand from there.

If your site feels polished in one place and improvised in another, show us the path a customer takes. We can help identify the few shared decisions that would make the whole experience feel like yours.