Web design

Design Systems and Style Guides for Websites: A Practical Starter

Design Systems and Style Guides for Websites: A Practical Starter: MeraSEO article cover
Key takeaways
  • A web style guide is a short document of decisions: colors, type sizes, spacing, components, icons and image rules, written down once so every page matches.
  • A small business site needs a one-to-three page guide, not a full enterprise design system.
  • Define values as named tokens (for example “primary”, “space-4”) instead of repeating hex codes and pixel values everywhere.
  • Keep icons and images lean: on our own site, subsetting icon fonts cut font weight per page by 56 to 75 percent.

Many websites start consistent and drift. A new page gets a slightly different blue, a button is a few pixels taller, a developer adds a second icon library. None of it is dramatic, but together it makes a site feel patched together, and it makes every future change slower.

A style guide fixes that by recording the decisions once. This post explains what to include, shows a worked example of design tokens, and gives a step-by-step way to build a guide for a small site without a dedicated design team.

Style guide vs design system: what is the difference?

A style guide documents how things look: colors, fonts, spacing, logo usage, image style. A design system goes further and includes reusable components (buttons, forms, cards, navigation) with rules for when to use each, usually with matching code. Large product teams need the full system. A business website with 10 to 50 pages usually needs a style guide plus a short component list, which is what this post covers.

What a web style guide contains

1. Color tokens

Choose a small palette and give each color a role rather than a name based on its appearance. A typical set is a primary color, a darker shade for hover states, an accent used sparingly, text colors, a background, a border color, and status colors for success, warning and error.

Check contrast when you choose. WCAG asks for at least 4.5:1 between normal body text and its background, and 3:1 for large text and interface elements. Light grey text on white and white text on a pale accent are the usual failures. Record the approved pairings, such as “white text on primary”, so nobody has to guess.

2. Type scale

Limit yourself to one or two font families. Define sizes for H1 to H3, body text, small text and buttons, with line height for each. Body text around 16 px with line height near 1.5 is a safe starting point. Write down the maximum line length too; roughly 60 to 75 characters reads comfortably.

Fonts are also a performance decision. Unless you use a variable font, every weight and style is another file to download: two families in three weights each is already six files before any icons. Most business sites need regular and bold for body text and at most one display weight for headings, so write the allowed weights into the guide.

3. Spacing scale

Choose a base unit and use only its multiples, for example 4 or 8 px. Margins, padding and gaps then come from a short list instead of ad hoc numbers. This is the single change that most quickly makes a page look tidy.

4. Components

List the parts used repeatedly and show their states: default, hover, focus, disabled and error.

  • Buttons: primary, secondary, text link. One primary button per section.
  • Forms: label position, field height, error message style, required marker.
  • Cards: image ratio, title length, link behavior.
  • Navigation: header, mobile menu, footer.
  • Alerts and notices: success, warning, error.

Include a focus style for keyboard users. Removing the browser’s focus outline without a replacement is a common accessibility mistake.

5. Icons

Pick one icon family and one stroke style, and set standard sizes (for instance 16, 24 and 32 px). Mixing outline and filled icons or two different libraries is an easy way to look inconsistent. Use icons next to text labels where meaning is not obvious, and never as the only clue for something important.

Icon fonts are convenient but often ship hundreds or thousands of glyphs you never use. On meraseo.in we subset the icon fonts to only the icons actually in use, which cut font weight per page by 56 to 75 percent. Inline SVG for a small set of icons is another lean option.

6. Imagery

Describe the photo style (real people and places over generic stock, consistent lighting), aspect ratios for each use, and rules for cropping. Set file rules as well: format, maximum width and compression. Our guide to WordPress image and layout dimensions suggests sizes for common slots such as heroes, cards and featured images. Convert images to WebP and size them to the slot they fill rather than loading full-size originals. For brand marks, logos and positioning, see building a brand identity.

A worked example: design tokens for a small site

A token is a named value. Instead of writing “#1b5e20” in forty places, you define “color-primary” once and reuse it. When the brand color changes, you edit one line. Here is a sample set for an imaginary consultancy site.

TokenExample valueUsed for
color-primary#1b5e20Primary buttons, links, key headings
color-text#222222Body copy
color-border#dfe3e8Table and card borders
font-body16 px / 1.5Paragraphs
space-2 / space-4 / space-68 / 16 / 24 pxGaps, padding, section spacing
radius-base6 pxButtons, cards, form fields

In a WordPress block theme, these map to the palette, font sizes and spacing presets in theme.json, which then appear in the Site Editor’s Styles panel. In Elementor, they go into Site Settings as Global Colors and Global Fonts. In custom code they become CSS custom properties, for example –color-primary. Either way, the point is that the choice lives in one place.

How to build one in six steps

  1. Audit what you have. Screenshot your key pages and list every color, font size and button style in use. You will usually find more variants than you expected.
  2. Pick the winners. Reduce to one primary color, one or two text colors, a type scale of six or seven sizes, and a single button style.
  3. Check contrast for every text and background pairing you plan to use.
  4. Define tokens and enter them in your theme or page builder as global settings.
  5. Document components with a screenshot, the do and don’t, and the states. A shared doc or a single hidden page on the site works well.
  6. Apply and enforce. Rebuild pages from the global styles, and review new pages against the guide before publishing.

This pairs naturally with a UX pass; the two are covered together in our UI/UX website design work, and graphics such as banners, icons and social images are covered under content creation and design.

Keeping the guide alive

A style guide only works if it stays current. Give it an owner, even if that is one person part-time. Date each change, keep a short list of what changed and why, and review it whenever you add a new page type, run a campaign with its own look, or hire a new designer or agency. When a one-off exception comes up, decide whether it should become a rule or stay a one-off, and write the answer down. A useful habit is to open the guide before every redesign discussion, so debates about taste start from the decisions already made.

Common mistakes

  • Too many fonts and weights. More files, slower pages, less consistency.
  • Documenting but not applying. A PDF nobody opens helps nobody. Set the styles in the theme itself.
  • Color without roles. A palette of ten unnamed colors invites random use.
  • Ignoring states. A design with no hover, focus or error states gets patched by whoever builds it.
  • Skipping the update rule. Decide who may change the guide and how, or it drifts again.

Frequently asked questions

What should a website style guide include?

At minimum: color palette with roles and contrast-checked pairings, type families and a size scale, a spacing scale, button and form styles with their states, icon rules, and image guidelines. Logo usage and tone of voice can be added if several people create content for the site.

Do small businesses need a design system?

Usually not a full one. A short style guide and a list of core components are enough for a site with dozens of pages. A fuller design system becomes worthwhile when several teams or products share the same interface and need reusable, coded components.

What are design tokens?

Design tokens are named values for design decisions, such as a primary color, a spacing step or a corner radius. Instead of repeating raw values across pages, you reference the name. Changing the token updates every place it is used, which makes rebranding and consistency far easier.

How do I keep my website visually consistent across pages?

Set colors, fonts and spacing as global styles in your theme or builder, reuse saved components rather than rebuilding them, and review new pages against the guide before they go live. Limiting the number of fonts, button styles and icon sets removes most inconsistency.

Need a consistent look across your site?

We can audit your current pages, define a practical style guide and apply it in your theme or builder.

See UI/UX website design →

Related Post

Call Now Button