Re: [community-group] [RFC] Theming (#2)

In terms of "defaults", I like to be prescriptive for the theme. Even if we have a primary brand theme, it is not based on default values, it's based on values specific for the theme. I think the "default" is there for when a theme fails. In the case of the web, perhaps it's better to have a default in to ensure the page is readable as the theme loads in.

```css
.my-danger-button:active {
    background-color: var(--backgroundColor-buttonCritical--pressed, '#f00');
}
```

The theme for the components may have failed in loading, so we fallback to the `#f00` which isn't part of any "theme", it's the default value. It's certainly possible that no change is detected; as in `--backgroundColor-buttonCritical--pressed`'s value could be `#f00`.

In the case of overriding, I think that's less of a design token issue and more of a permissions issue. Design tokens are shared values for a managed design system; if you don't want to use those values, then you are simply deciding on different values. However, if the tool's permissions say you *must use these tokens only* (with some leeway in approved places), then I think that's a separate topic. I think what's being asked for here is a method of accessing predetermined values in design tools as well as custom values.

-- 
GitHub Notification of comment by ddamato
Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/2#issuecomment-528929380 using your GitHub account

Received on Friday, 6 September 2019 16:49:26 UTC