Skip to content
ColorArchive
Notes · Workflow

Workflow

8 issues tagged with this topic.

Issue 0172026-03-28

Color accessibility beyond WCAG minimums: what the numbers miss

Why passing WCAG contrast ratios does not guarantee a readable palette, what the numbers cannot measure, and how to audit a color system for real-world accessibility beyond the 4.5:1 threshold.

AccessibilityUIWorkflow
Issue 0162026-03-27

Color in data visualization: clarity over decoration

Why chart color systems fail when they prioritize beauty over function, how chroma control keeps categories readable, and where the Complete Archive provides a consistent categorical palette source.

ToolsUIWorkflow
Issue 0132026-03-24

Color naming that sticks: from mood labels to production-grade tokens

Why ad-hoc color names collapse under scale, how role-based naming survives redesigns, and where the All Access Bundle removes the naming architecture overhead entirely.

TokensWorkflowNaming
Issue 0102026-03-21

Color workflow automation: from hand-picked swatches to token pipeline

Why manual color handoff breaks down, how Modern Seaside illustrates the gap between a curated palette and a production-ready token set, and where the Complete Archive fits as the pipeline source.

WorkflowToolsFigma
Issue 0072026-03-18

Design tokens that don't drift across CSS, Tailwind, and Figma

Why token exports break after handoff, how to keep reference and alias layers aligned, and where the All Access Bundle fits when a team needs one color source of truth.

FigmaTokensWorkflow
Issue 0492026-12-03

How to document a color palette so the next designer can use it

A palette that exists only in a Figma file is a palette that will be misused the moment the original designer leaves the project. Color documentation is the difference between a palette that lasts and one that drifts.

Design SystemsDocumentationWorkflow
Issue 0512026-12-17

Print vs. screen: why your colors look different and how to manage the gap

Designing across both print and digital means managing the fundamental incompatibility between subtractive and additive color. Most designers learn this the hard way on their first print project. Here is the framework for managing it intentionally.

Print DesignColor ScienceWorkflow
Issue 0752027-06-17

RGB, CMYK, HSL: which color mode you should actually design in

Color modes are not interchangeable descriptions of the same thing. They are different mathematical models for describing color, each built for a different output medium and workflow. RGB is additive — light mixed together. CMYK is subtractive — inks mixed on paper. HSL is perceptual — how designers actually think about color. Choosing the wrong mode for your context produces predictable problems: colors that look right on screen and wrong in print, brand colors that cannot be consistently replicated, and palette adjustments that are impossible to describe verbally to a developer. Understanding when to use each model — and how they relate to each other — is a foundational design skill.

Color TheoryWorkflow
Browse other topics