Content
@
0 reply
0 recast
0 reaction
typeof.eth 🔵
@typeof.eth
Maybe hot take, but I really don't see the point of having ~10 shades per color in a design system. Do we need more than foreground/background/hover variants for every single color? I can see the case for more grays, maybe. Curious what y'all think.
9 replies
1 recast
9 reactions
Darryl Yeo 🛠️
@darrylyeo
Now that we have color-mix(), we really only need to define one or two base accent colors then derive any variants we need dynamically. https://developer.mozilla.org/en-US/docs/Web/CSS/color_value/color-mix
2 replies
0 recast
3 reactions
typeof.eth 🔵
@typeof.eth
I love that this is available natively, but IMO it doesn't answer the question of how many shades per color to use. I.e. it's a great way to create shades, but IMO it's still a good practice to limit their number to a consistent set.
2 replies
0 recast
0 reaction
Darryl Yeo 🛠️
@darrylyeo
Agreed, better to define just enough colors to meet minimum semantic/accessibility needs – a different hue for every distinct meaning (default/accented/success/error) multiplied by one shade variant for each interactive state (default/hover/active) multiplied by the number of themes you want to support (light/dark).
1 reply
0 recast
1 reaction
Marc BHE Season 🍖☣️
@bighamenergy.eth
I don’t use shades. Because color-mix can be used at 20,40,60,80 and this is a 6 tone palette. And I can still make it 8 by adding 2 tones more. Now i focus more on meaning like “foreground” “accent” or this naming so i can replace them
0 reply
0 recast
1 reaction
