[bug] rgb values, overlay tokens

[zeroedin]

In rh-table we are using transparencies with various crayon tokens. Even though we try and avoid using crayons in components, we are using them there because they provide RGB values to which we can apply opacity.

We are also using #FFFFFF or --rh-color-white which does not provide RGB values. I have created a --_rh-color-white-rgb private var as a place holder for now.

Should we though ensure all base crayon colors have RGB values?

Do we think we should abstract these RGB values into overlay tokens which provide could provide additional semantic layer so they would be used in a component instead of the crayon? I envision some difficulty in abstracting the color values + opacity level in doing so to the name of the tokens.

[bennypowers]

Would oklch (why?) be of interest to our studio designers? This could be an interesting avenue to pursue in the new year.

[zeroedin]

This could be an interesting avenue to pursue in the new year.

I like this, could be a good solution.

[marionnegp]

Would oklch (why?) be of interest to our studio designers?

Would this replace our -rgb and -hsl tokens? Not sure how helpful oklch would be until it can be used within our design tools.

[zeroedin]

Because I was doing some investigation on this myself today. @marionnegp I wonder if any of these plugins would be helpful to move this forward?

https://www.figma.com/community/plugin/1173638098109123591/okcolor

https://www.figma.com/community/plugin/1418444633232614903/ok-palette