Skip to content

Introducing design tokens for commonly used colors #14780

@chrifro

Description

@chrifro

Why should we use design tokens for colors?

  • one of the first steps to a design system
  • helps to keep a consistent design: no more color guessing, just apply the predefined color.
  • automatic adjustments for different themes: once defined, select a token that's automatically adjusted for all themes
  • easy to adjust if we ever decide to change color: instead of adjusting all text fields, we'd only need to adjust the design token.

How does it work?

  1. create color primitives based on the Tailwind CSS color library
  2. create color tokens and assign primitives for each theme to it
  3. assign the color tokens to all content

How do I know which color token I should assign to a content piece?

  • the naming convention should help to identify the use case
  • additionally, you can find an overview of how to apply the new colors to existing designs here in Figma

Scope
I'd suggest we start with the most basic color styles: content-xyz, surface-xyz, and border-xyz. We can build on it as we go.

Note
I tested the colors for all themes for the most common screens and made sure they pass accessibility requirements. In case, you find a place nevertheless where the colors don't fit well, let me know :)

Resources
Image
Image
Image

Metadata

Metadata

Assignees

Labels

design readydesign is approved and ready for implementation

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions

    pFad - Phonifier reborn

    Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

    Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


    Alternative Proxies:

    Alternative Proxy

    pFad Proxy

    pFad v3 Proxy

    pFad v4 Proxy