- From: Nate Baldwin via GitHub <sysbot+gh@w3.org>
- Date: Wed, 18 Sep 2019 16:26:34 +0000
- To: public-design-tokens-log@w3.org
@applinist I love this. That's in line with how we're thinking as well. Speaking to this as a "system state" is a nice way of consolidating those terms as they are a similar model. I agree with the notion of overrides as you mention them in your tables. I'm not sure I would qualify those as "overrides" in the cases where no token value is assigned for a particular state variation (ie, "contrast_low" has no value for tokenA, therefore it's not an "override"). I am of the opinion that systems authoring needs to support a model that allows for crazy-complex situations like what you're alluding to. Companies and brands have a variety of ways in which they want to strategize the implementation of a "theme", and conceptualizing this as "system states", which can be exponentially compounded is a flexible solution that will more-often-than-not show itself as simply a "light mode"/"dark mode" paradigm. It's simple enough that it doesn't overcomplicate this use case. -- GitHub Notification of comment by NateBaldwinDesign Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/2#issuecomment-532761746 using your GitHub account
Received on Wednesday, 18 September 2019 16:26:35 UTC