- From: Miriam Suzanne via GitHub <sysbot+gh@w3.org>
- Date: Tue, 20 Aug 2019 01:19:35 +0000
- To: public-design-tokens-log@w3.org
Hey all 👋 – I work on Sass, Accoutrement, and Herman. Glad to see this happening! Thanks for the invite @kaelig. I tend towards the keep-it-simple suggestions above - with a concern for writing-by-hand. In my experience design systems have to be co-maintained by designers and developers (including CSS developers) across a range of contexts. While it's great (and necessary) to build tooling around the format – I would find it much less useful if it *requires* tooling to write/maintain easily. And I'll follow that up by adding some complexity. 😬 I think alias references are necessary, but only a half solution. Design systems should be able to store meaningful relationships that include *adjustment* of values: e.g. `space2 = space1 * 2`. If I can't capture real relationships, it doesn't feel like a system - it's just a list of keys and values. I realize that becomes much more complex when you start thinking about color-spaces, and the meaning of a term like "lighten" – but something to consider… -- GitHub Notification of comment by mirisuzanne Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/1#issuecomment-522813334 using your GitHub account
Received on Tuesday, 20 August 2019 01:19:37 UTC