- From: Alexander Vassbotn Røyne-Helgesen via GitHub <sysbot+gh@w3.org>
- Date: Mon, 05 Jun 2023 07:16:16 +0000
- To: public-design-tokens-log@w3.org
@ipaintcode The road you've started to tread has many pitfalls :P I've been trying to bridge the designer/developer waters for a very long time, and I always come to the same conclusion, it's not possible, for now. But, luckily, the usage of design tokens is a tool that minimized the pains for that communication. I've held a couple of talks regarding design tokens and how designers and developers speaks different languages. They also have different cultures and where those professions originated from. I think the purpose of design tokens (where a design token contract is one option) is to minimize the secondary activities we have when communicating design and code. The concept of design tokens is inherited from what developer has had for years, variables. And we have to remember that design tokens is a way of communicating design, but within a code context. I think it's easier to say that design tokens is the interface (or glue) that sticks between design and code. In my experience, it all boils down to where the source of truth is defined, and that is done per project, or per design system (not everyone uses or should use a design system). Continuing with my experience, no designer, ever, has the capacity to always maintain design sketches (best example is in a design system team), but a developer can update and maintain code more easily. Design **System** decisions are made by a team, and then the change is implemented, in code and in the sketches. Design tokens helps a lot with those changes. What I'm trying to say is that designers and developers should not dictate each other, they should work in tandem, and make multi-disciplinary decisions together as a team. -- GitHub Notification of comment by phun-ky Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/220#issuecomment-1576187104 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 5 June 2023 07:16:17 UTC