- From: Alexander Vassbotn Røyne-Helgesen via GitHub <sysbot+gh@w3.org>
- Date: Sun, 26 Sep 2021 07:20:12 +0000
- To: public-design-tokens-log@w3.org
@nagueva > design tokens are the best way to soften the communication between design and development It is also to soften communication between developer and designer. The communication should be a loop between the two parties, not just from the designer to the developer. It's been far too long that the idea of design communication is only from the designer to the dev. Ive been doing frontend since 1998,so I've experienced my fair share of this. A designer rarely knows the limitations of or implications of the design provided. A dev (and perhaps ux) does. And from what I've pointed out under #43, creating and maintaining tokens rarely falls under the designer role. I have evangelized, for a time now, that we need to bridge the gap between designers and developers. We don't share the same language, we rarely sit together in the same team etc. Design tokens could be the key, or start, to help with this. My utopian vision is that design and develop communication works as a continuous loop : (agreed upon) changes (tokens?) in a component by a dev should automatically be reflected in the design kit/sketches /lib, and any (agreed upon) changes (tokens?) in the design should also be reflected in the code. -- GitHub Notification of comment by phun-ky Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/32#issuecomment-927248916 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 07:20:15 UTC