- From: Alexander Vassbotn Røyne-Helgesen via GitHub <sysbot+gh@w3.org>
- Date: Sun, 26 Sep 2021 13:45:47 +0000
- To: public-design-tokens-log@w3.org
> These statements are definitely not true in my experience, including at Salesforce where design tokens were concepted. Yes, I can understand and respect that, but different cultures and company/team situations apply here. In my DS team, the tokens are identified by the developers. But that is not the case for all teams/companies/cultures. > I find this very offensive, to be honest. I'm a designer, and I helped develop and architect several token systems, including how it manifests in code. And I really do apologize for my offensiveness, but that was never my intention. And I was very clear that I "put it to the extremes". This statement was from my experience, and as I stated earlier in a different thread, I am very happy to see that you've experienced it differently, and I'm humbly envious of your situation. I am not trying to be gatekeeping or non inclusive here. If that was what I came across like, that's my bad. > So this thread was more about for THAT particular workflow, what kinds of things would people like? Obviously, this wasn't addressing the dev-centric workflow, which some people are much more familiar with. So, I am happy to take hold of the "The developers workflow", as an issue here, if that is acceptable? Not trying to step on any toes here. Just eager to help <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-927309314 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 26 September 2021 13:45:49 UTC