You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, our Tailwind CSS brand values are specific to the colors they represent; e.g., bluedot-lighter.
I would like us to adopt a more generic naming system, e.g. bluedot-primary, bluedot-secondary, etc. so that we are set up to adapt more rapidly to changing design system requirements.
I recommend doing this in a backwards compatible manner; i.e., add the new values to the existing list and map them all to CSS vars:
tarinrickett
changed the title
Refactor Tailwind values for robustness
Add CSS vars and refactor Tailwind values for robustness
Jan 21, 2025
tarinrickett
changed the title
Add CSS vars and refactor Tailwind values for robustness
Add CSS vars and refactor Tailwind brand values for robustness
Jan 21, 2025
Currently, our Tailwind CSS brand values are specific to the colors they represent; e.g.,
bluedot-lighter
.I would like us to adopt a more generic naming system, e.g.
bluedot-primary
,bluedot-secondary
, etc. so that we are set up to adapt more rapidly to changing design system requirements.I recommend doing this in a backwards compatible manner; i.e., add the new values to the existing list and map them all to CSS vars:
Open to discussion here!
This is not just for color tokens – we should also update for standard grid sizes (incl. width, padding, margins, etc.), font sizes (s/m/l), etc.
The text was updated successfully, but these errors were encountered: