Re: [community-group] Add "Option" and "Alias" token clusters (#145)

Hope that this is relevant to the discussion, because I can relate to @reblim point. We call the "option tokens" "base tokens" or "raw tokens" because they hold raw value and their naming convention follow the Category Type Item system. The "aliases" are split into 3 categories to convey the design intent, and these tokens can only inherit from the parent level. This allow us to have a specific naming convention at each level depending on the audience that will use them. 

I don't know if @reblim proposal has to be in the specs in order to build an appropriate token architecture, I think it depends on the complexity of the project. For us because we are federated and distributed, we needed a way to convey to 5000 designers and developers how to build their own components while keeping the brand consistent and maintainable by a team of 20 token maintainers.
![image](https://user-images.githubusercontent.com/2599251/178934585-9e719e5f-439e-4a4c-b16f-2988429be62e.png)

At different level we have a "cluster" of tokens that can be used by different audiences in their mental model. This approach may be overkill in a team of 1.
```
{
ds: {
  base: {
    color: {
      orange: {
        200:  {
          $value: rgb(232, 86, 79, 1),
          $type: color
        }
      }
    }
  },
  standard: {
    color: {
      action: {
          $value: {ds.base.color.orange.200},
          $type: color
      }
    }
  },
  component: {
    button: {
      action: {
        background: {
          color: {
             $value: {ds.standard.color.action},
             $type: color
          }
        }
      }
    }
  }
}
```
For us the second level of the token is documented to convey where we accept raw values or aliases. Do we want to make it explicit or not with a spec? I could see the value of having only one source of truth, but for how many people have that use case? I wonder. 



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


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

Received on Thursday, 14 July 2022 14:38:01 UTC