Open dmfalke opened 2 years ago
i love this idea. Even here in github we can see some buttons are in the main color and some are in grayscale. Same with using google docs, and confluence.
Thinking aloud: one option to get grays/neutrals into the palette is to say our secondary color will be a neutral. Then we have colored and neutral buttons and that's it. Pro: very simple palette since it's really just one main "color" and a neutral. Confluence seems to basically do this. Con: limits expression ability of our palette. Our site is more complicated than confluence or google docs so i think having a non-neutral color in the secondary color slot would be helpful. So right that brings us to adding a third theme role. I'd consider calling it "neutral" instead of "grayscale", because we might want it to be tan or a different shade of gray sometimes (the undertones in the gray should vary based on the primary and secondary colors).
I also think the default disabled color could be drawn from this third themeRole. Whether it always needs to be the 300 level of the hue or we should specify it directly im not sure of yet, but either way i think it should have the same hue as this third themeRole.
I think there are cases where we want to use grayscale widgets (icons, some buttons, etc). It might be nice allow this to be specified as a themeRole.