The Gutenberg editor relies on hard-coded color values in the color selection, which can make it difficult to stay consistent on a site, especially when a theme or global color scheme is updated, Colors changing in many places takes time for users and developers. Additionally, changes to variations don’t propagate, creating custom CSS for color modes doesn’t function as expected, and child theme JSON files fail to apply changes globally.
What Is Your Proposed Solution?
The proposed solution is to incorporate CSS variables for color values within the Gutenberg editor. Since variables are already created for custom, theme, and default colors in global styles, utilizing them can simplify the process. CSS variables would allow for seamless updates from variations, and child themes, including custom modes. This approach would simplify the management of color schemes, ensure consistency across the site, and reduce the need for manual adjustments.
What Problem Does This Address?
The Gutenberg editor relies on hard-coded color values in the color selection, which can make it difficult to stay consistent on a site, especially when a theme or global color scheme is updated, Colors changing in many places takes time for users and developers. Additionally, changes to variations don’t propagate, creating custom CSS for color modes doesn’t function as expected, and child theme JSON files fail to apply changes globally.
What Is Your Proposed Solution?
The proposed solution is to incorporate CSS variables for color values within the Gutenberg editor. Since variables are already created for custom, theme, and default colors in global styles, utilizing them can simplify the process. CSS variables would allow for seamless updates from variations, and child themes, including custom modes. This approach would simplify the management of color schemes, ensure consistency across the site, and reduce the need for manual adjustments.