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
Alex Bruno
@alex
It could depend on your treatment of color. High-contrast style can get away w/ fewer variants. Opacity could go a long way in creating the illusion of shades (e.g. Warpcast). Sometimes inverting colors won't always work for dark mode, so you might need separate values for that
1 reply
0 recast
1 reaction
typeof.eth 🔵
@typeof.eth
Yeah, I think what I wanna propose for the design system we're building out at Iron Fish is separating colors into background/foreground/active for both light and dark mode, and making sure that those are all a11y friendly. But like, we really shouldn't need more than 3 variants per color scheme, right?
1 reply
0 recast
1 reaction
Alex Bruno
@alex
Yeah, I can see that being pretty versatile. For example: Light/Primary/Background Light/Primary/Foreground Light/Primary/Hover Light/Primary/Active Same for secondary/neutral/etc in light and dark. You can use opacity for inactive states How about surfaces? Background/foreground naming could get confusing
1 reply
0 recast
1 reaction
typeof.eth 🔵
@typeof.eth
Yeah, the naming isn't great, hah. Tbh, I wish there was some opinionated "implementation-less" design system that was like: - Define these tokens - Create these components - Ensure these accessibility guidelines Boom, you got yourself a design system
0 reply
0 recast
1 reaction
