Continuing the discussion from Cleaning up our color palette :artist_palette:: [image]Cleaning up our color palette artist_palette alongside the ability to override those variables from a theme. Themes already have the ability to define sass variables: spec/models/remote_theme_spec.rb main }, "color_schemes": { "#{color_scheme_name}": { "love": "#{love_color}", "tertiary-low": "#{tertiary_low_color}" } }, "modifiers": { However, from personal testing, these seem to be local to the theme’s stylesheets, and won’t globally override a variable. If they did it would prove incredibly useful for theme development, as it would allow the theme to specify exactly what colour should be used as $primary-medium, $tertiary-low and so on - rather than have it automagically calculated off of the colour scheme. Perhaps there should be a scope option, something like this: "fields": { "primary-medium": { "value": "#012345", "type": "color", "scope": "global" } }

Maybe, but what happens if multiple theme components are fighting for such a change, who wins?

As a wise man once said: [image]Simplified HTML emails I think that is imagining a problem that will, in practice, never exist I can’t see much use for this beyond colours, and I can’t ever see a user wanting to enable two themes both of which change the color scheme. Perhaps though this makes more sense as an extension to color_schemes, which can only be enabled individually: "color_schemes": { "Extened Scheme": { "primary": "000", "primary-medium": "666", "primary-low": "aaaaaa" } }

Related: [image] Request: Turn color schemes off in the admin area Feature Request: The color schemes should be completely switched off in the admin area or switch to the default. Reason: Many pages use the Color Schemes in combination with Custom CSS to create the desired effects. Since the CSS in the admin area is switched off, it looks in part ugly and has a bad usability.

I really need this. I have a default primary colour: 4d238c. The issue is the color for $primary-secondary that is being generated (#a179de) doesn’t pass accessability guidelines, so i need to make it darker, It seems laborious to change it in all places where the system is using the secondary colour when I could just over write $primary-secondary : red;

You can now override the automatically generated variables in a remote theme: Override values for auto-generated color variables

Override global Sass variables from theme

Development

erlend_sh (Erlend Sogge Heggen) August 17, 2017, 3:39pm 4

Topic		Replies	Views
Override programmatic color generation Product Support	4	1843	November 25, 2019
Override values for auto-generated color variables Announcements	0	2131	November 25, 2019
How to overrule a color variable for one theme only? Development	8	2266	February 2, 2020
Change all the colors of a theme Product Support	1	873	May 13, 2022
Is there a way to overwrites all colors? UX	3	1542	November 25, 2019

Override global Sass variables from theme

Related topics