- From: Kaelig Deloumeau-Prigent via GitHub <sysbot+gh@w3.org>
- Date: Sat, 10 Dec 2022 06:28:23 +0000
- To: public-design-tokens-log@w3.org
Thank you for raising this, and I can say this dilemma came up frequently in our meetings! If we take SVG as an example, I've been saying things along the lines of: _some of us have drawn icons using SVG by hand, but none of us really **want** to, especially for more advanced cases._ As for readability/editability: unless it's a very simple shape, it's impossible to read an SVG file and draw a mental picture of its visual output. That's why we use tools to create pictures and then export them to SVG (in a lossy way) for interoperability. On the other hand, CSS is quite different in that it's much more optimized for editability and readability. For now, we typically want humans to be able to author and edit CSS (that said, with the rise of AI in the creative process, I don't know that people will manually write much CSS in the future). Some exceptions apply to gradients and perhaps shadows, where the syntax can get so complex that tools help a lot. When Jina, Garth, Danny and I started this group, we discussed what our principles should be from a technical and community perspective. At the time we were convinced that we should lean more toward the CSS model than the SVG model. I think it's still relevant today to meet people where they are, but I expect things might evolve once we have much better tooling around. -- GitHub Notification of comment by kaelig Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/149#issuecomment-1345154841 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 10 December 2022 06:28:25 UTC