There are two hairy issues with our current implementation of color schemes:
- color schemes are globally available to every theme and are not theme specific.
- offering more than one user-selectable color scheme for a theme requires you to “duplicate” the theme as a separate entity
Neither of the above should be true.
It is far more common for a site (or app) to offer multiple color schemes (most commonly one light and one dark) rather than multiple themes; practically all companies will just want to maintain a single theme that is tailored to their branding.
The way we handle color schemes right now is confusing. Selecting a color scheme in our wizard will create a new-standalone theme for that color scheme. To find those other color schemes I need to re-do the wizard. What’s more, once I’ve redone the wizard and selected a new color scheme, I’ve actually just added an identical theme which happens to have a different color scheme set as its default:
While the theme “Latte” has the default color scheme of “Latte”, I can set that color scheme to “Neutral”, “Light”, whatever.
“Latte” shouldn’t be a theme. It should be a color scheme specific to our default theme, which it was specifically designed for.
The color schemes editor should look more like this:
Just to reiterate: Color schemes should be theme-specific:
- Our default theme should have its own distinct color schemes
- Material theme should have its own distinct color schemes
- Classic theme should have its own distinct color schemes