Re: [community-group] colorPalette composite type (#178)

> it's not always multiples of 10s. … There's also many cases that omit or add steps based on the luminosity

That’s a very great point. There is no one true way of deriving these values, and even the most methodical systems do have half-steps like you said.

The array approach is more of a very practical usage of a color gradient, because take away all the keys and you do have stepped color that you usually adjust by a value or two to get the right contrast. And so this proposal would be to have a more generic approach by not getting into the differences of those keys.

But also to your point, those keys are important to some systems, and do carry meaning. And for those systems I guess that would just be better served with groups that exist in the spec now. But I’d still think that many systems do operate like more of an array, and regardless of absolute values between the steps, do think of the gradient more like a type scale, and often step “up” or “down” more fluidly as needed.

> Is the suggestion to limit to only three values (light, mid, dark)? I've found often that's not enough.

To be honest this was more a half-baked attempt at interpolating colors, but after reading your thoughts I’m thinking that won’t be practically possible. So I’d probably just say “let’s forget about the semantic boundary approach” 😄

-- 
GitHub Notification of comment by drwpow
Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/178#issuecomment-1306574111 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 8 November 2022 03:22:37 UTC