Re: [community-group] The Designer’s Workflow (#43)

Oookay. A lot of great discussions here and I must admit I had to scim trough most of it, so sorry in advance if my comment seem redundant.

Again, I see a lot of bias here towards design token being a design-only token upon creation. Design token definitions are data, regardless of the format it is provided in (JSON, yml, csv), and it needs to be processed regardless of end user; designer in a design tool, developer in an editor or IDE and reader of the documentation.

From my perspective, most likely tokens are created and found by devs in a DS, not designers. Designers (i am putting it to the extremes here, so sorry) rarely know what can be in a token and what can't be in the token. They have not the full grasp of what the whole DS is,the capabilities and limitations, because that is set in code.

A DS team does not agree upon tokens, they agree upon parts of a design system that can be used as a token and then processed to variables or documentation. 

Design tokens, upon creation, needs to be versioned, and then, only then, it is the source of truth. 

I might seem cranky here, but I just want my concerns to be heard. Much love <3 

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


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

Received on Saturday, 25 September 2021 09:24:46 UTC