Notes · Tokens
Tokens
9 issues tagged with this topic.
Issue 0232026-04-23
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.
SystemsBrandTokens
Issue 0182026-03-29
Monochrome color systems that do not look flat: contrast, texture, and role separation
Why single-hue systems collapse under real product conditions, how to create enough visual separation without introducing secondary hues, and where the Complete Archive token structure handles the layering work.
PaletteUITokens
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 0082026-03-19
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.
BrandTokensSystems
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 0052026-03-16
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.
BrandTokensSystems
Issue 0012026-03-12
Matcha & Linen, calm product surfaces, and what shipped in March
A monthly ColorArchive note covering a calm green editorial direction, the archive's new account layer, and live token exports.
WellnessAccountTokens
Issue 0272026-05-21
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.
SystemsTokensProcess
Issue 0332026-07-02
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.
TokensSystemsDevelopment
Browse other topics