Palette and Typography
Brand Color Systems: From Palette to Functional Framework
Five beautiful colors do not make a system. How to build a brand color system: roles, proportions, contrast, and design tokens that translate directly to the web.
For designers
3min read
·

Delivering five color swatches in a row with hex codes is not a color system. It is merely a palette. The difference surfaces at the first implementation: Which color serves as the background? Which applies to the primary button? Can white text sit on yellow? If the palette fails to answer, every designer will answer differently.
From Palette to System
A palette defines what the colors are. A system defines how they function: their roles, proportions, and permitted pairings. Selecting the colors themselves was covered in Color Palette. This article addresses what comes after selection.
Roles

Assign every color a distinct function, not merely a name:
Primary: The core brand color. Anchors the logo and primary brand elements.
Secondary: Supports the primary color and broadens expressive range.
Neutral: Backgrounds and typography. Occupies the majority of visual real estate, yet remains overlooked in most palettes.
Accent: Used sparingly for high-emphasis moments: buttons, key metrics, critical notifications.
Functional: Success, warning, error. Required for interfaces and must never conflict with core brand colors.
Proportions
Proportions shape the brand atmosphere. The identical palette yields a refined, understated brand when dominated by neutrals, or an aggressive one when dominated by the primary tone. Define an approximate distribution: neutral, primary, and accent allocations. Represent this visually in the guidelines, as raw percentages alone fail to convey intent.
Contrast and Legibility
Every text-and-background pairing requires validation prior to approval. WCAG guidelines mandate a contrast ratio of at least 4.5:1 for body copy and 3:1 for large text at Level AA. Include an explicit matrix of permitted and prohibited pairings within the brand guidelines to prevent legibility failures post-launch or print.
Account for high-risk combinations: white text on yellow, low-contrast gray for secondary text, and typography placed over imagery.
Tonal Scales
A single value is insufficient for product interfaces. Every primary color requires a structured tonal scale from light to dark, calibrated in visually uniform steps. Lighter shades serve backgrounds, mid-tones define borders, and deeper shades handle text and active states. Build and document the scale systematically to prevent ad hoc value creation.
Print to Screen
A single color requires multiple technical definitions:
HEX and RGB for digital screens.
CMYK for standard process printing.
Pantone for spot-color precision across physical substrates.
Automated profile conversions produce dull results, particularly across saturated hues. Calibrate each color space manually and evaluate against physical drawdowns wherever possible.
Design Tokens

This is where a design system becomes operational software. Instead of hardcoding color values, assign them semantic tokens that describe functional intent:
Global tier (values): red-500, neutral-100.
Semantic tier (roles): surface-primary, text-default, button-primary-bg.
Components consume semantic tokens exclusively. When a color changes, it updates in a single source of truth. These exact token structures mirror across Figma and production code, transforming the digital product into a direct extension of the brand identity, as discussed in A Website Built on the Identity System Itself.
Dark Mode
If required, dark mode is never a simple inversion of lightness values. Dark surfaces demand desaturated tones and recalibrated contrast ratios. A structured semantic token architecture allows for dark mode implementation without rebuilding foundational components.
Documentation
Within Brand Guidelines, the color system requires at least four dedicated sections: core colors and color spaces, functional roles and proportions, approved pairings, and explicit use cases demonstrating correct and incorrect applications.
Common Pitfalls
An excess of colors without clear hierarchy.
Undefined neutrals, resulting in arbitrary blacks and grays.
Overused accent colors that dilute visual hierarchy.
Inconsistent color values across production files.
Summary
A color system is measured by whether an external partner can implement it correctly without asking questions. Defined roles, deliberate proportions, contrast compliance, and semantic tokens. For an applied case study on selecting accessible primary colors, refer to Five Lessons from the Design102 Identity Refresh.
