Re: [community-group] Color first draft (updated) (#266)

@lukasoppermann great questions!

> it is not shown in the examples, but can we add alpha when referencing colors? This is extremely important, as this is impossible with the current setup.

I think this should be addressed in the format module, not in the color module. I'm all for being able to pick parts of a token out (ie, in your example, picking the `components` out of `{base.color.black}`. There's been a few references to using JSON pointer notation here to allow more precision when referencing other parts of a token file.

cc @c1rrus 

> Also are we sure about using components as a name for the color values? To me this sounds unexpected, and I am wondering if this makes tokens hard to read for people who just contribute to tokens occasionally. Couldn't we use something like values?

This has been the topic of some debate; `components` is the preferred nomenclature in [CSS Color Module Level 4](https://www.w3.org/TR/css-color-4/#color-type), which is what we've used as a foundational spec. `channels` is another alternative, and I'm only slightly inclined towards components as it's also the preferred term in SwiftUI and Kotlin's docs. Happy to bikeshed more but would love to move quickly towards a decsion (see this comment from Jan 2023: https://github.com/design-tokens/community-group/issues/79#issuecomment-1402222582)

-- 
GitHub Notification of comment by ilikescience
Please view or discuss this issue at https://github.com/design-tokens/community-group/pull/266#issuecomment-2783394193 using your GitHub account


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

Received on Monday, 7 April 2025 13:43:58 UTC