Systems
9 issues tagged with this topic.
Building a color system that survives a rebrand
Most design systems treat color as fixed brand constants, which means a rebrand forces a rebuild from scratch. A resilient token architecture separates structural roles from brand expression, so the system adapts to new colors without breaking components or accessibility contracts.
Seasonal palettes beyond spring: building a rotation your brand can reuse
How to turn a one-off seasonal palette into a repeatable system, why Sunset Boulevard anchors a warm-season lane, and where the Spring 2026 pack fits as the first installment.
Brand color tokens are what stop marketing and product from drifting apart
A note on role naming, palette governance, and why brand color systems fail once the landing page, product UI, and campaign work all diverge into separate files.
Building a brand color system that actually holds up at scale
How to move from a single hex value to a structured brand palette — token naming, role definition, and the common failure modes that kill consistency before launch.
The case for limiting your palette to five colors
Unlimited color freedom produces worse palettes than deliberate constraint. The five-color ceiling is not an aesthetic preference — it is a cognitive and systems design limit. Understanding why the constraint works makes it easier to apply and defend in team settings.
Color naming is a systems design decision, not a branding exercise
How you name colors in a design system determines how teams reason about them, how documentation stays current, and how onboarding scales. Semantic names age well; descriptive names create maintenance debt. The naming strategy you choose in week one will shape token discussions for years.
How many colors does a palette actually need? The case for hue span constraints
Most product palettes are over-specified — too many hues, too many lightness variants, too many one-off accent colors. Understanding hue span as a design constraint produces palettes that are both more coherent and easier to use across a whole product.
The 60-30-10 ratio is a heuristic, not a law — but it points at something real
Interior designers talk about color distribution as 60% dominant, 30% secondary, 10% accent. The specific numbers are not sacred, but the underlying logic — that a small high-saturation color should be balanced by a large neutral — applies cleanly to interface design.
Why semantic color tokens are worth the extra naming effort
Raw hex values in a stylesheet are a maintenance liability. Semantic tokens — names like --color-surface-primary or --color-action-default — decouple intent from implementation and make design system changes much cheaper. The naming effort pays for itself the first time you change a theme.