- From: David Aerne via GitHub <sysbot+gh@w3.org>
- Date: Wed, 25 May 2022 09:48:39 +0000
- To: public-design-tokens-log@w3.org
I played around with that idea for small design research project for a client of mine: https://codepen.io/meodai/pen/WNjKzbp?editors=0010 It is implemented differently but the idea is the same. I like the proposal @c1rrus made using `$operations`. But In reality I found it a bit difficult to work like that with some designers. Because most had an awesome understanding of color theory but only a basic understanding of how the different color-models work. Thats why I would like to explore something that works a bit like reference- and value-tokens. Where a `$operation` would be a string that points to a function that is defined elsewhere, like @markuslangl proposed. I think it makes the communication across teams and roles a lot easier, because it would allow us to talk about the abstract idea rather than its implementation. Every designer I know, knows what a complementary color is, or the best contrasting color on a certain background. But how to actually implement that can be quite technical, and its implementation sometimes requires pretty complex functions. I tend to call this concept a "Rule Token" because I identified two main use cases: A function that produces a "value" just like the proposed operations, but also a function that returns a reference for example `cardText (onCard): "whatever color from collection X that has is the most readable on cardBackground" -- GitHub Notification of comment by meodai Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/88#issuecomment-1137031619 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 25 May 2022 09:48:40 UTC