You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey David - I was thinking more about (a previous issue I added) the customizer setting and my friction points as a designer /developer (as opposed to someone who needs the customizer).
Might there be SASS files for what the customize produces?
For example, currently, if the style guide (formal or informal) I'm working off of has a primary color and that color changes, then I need to find / remember all the place in the customizer it's used. Instead, if there were SASS files, I could update the $primary-color value and it would cascade. Mind you, I get it, I'd have to assign the $variables to the properties (as I would in the customizer), I get that :) But even that for me is easier than driling up and down and around in the customizer. Sometimes I get dizzy from that :)
Funny, this is similar to the discussion about headings and font sizes. Ultimately, I'm using the a layer of abstraction, which can add an extra layer - of confusion? - to the customizer. I think I saw something about a future color pallet feature. Maybe that'll help? But I think I'd still like to have the SASS, if it's avaiilable. Or even just all the CSS the customizer might render. I can reverse engineer the SASS from that, I hope :)
The text was updated successfully, but these errors were encountered:
Honestly, I had the same thought back then. I called it the "Global Colors" system. So the workflow would be like this:
User can add unlimited colors in the "Global Colors", for example:
Primary: #ffcc00
Secondary: #00ccff
And then when customizing the page, e.g. button background color setting, the user will have these choices:
Primary
Secondary
Custom (manual colorpicker)
Let's say the user chooses "Primary".
Then if we go back to the "Global Colors" settings and change the "Primary" color into #ccff00, then all color options that are set to "Primary" will also change to the new color.
This is my original thought on Color Palette feature. But I found it quite hard to implement, and I'm not sure if people think this workflow easier than the manual one.
So currently the Color Palette only works as a shortcut to choose colors.
Hey David - I was thinking more about (a previous issue I added) the customizer setting and my friction points as a designer /developer (as opposed to someone who needs the customizer).
Might there be SASS files for what the customize produces?
For example, currently, if the style guide (formal or informal) I'm working off of has a primary color and that color changes, then I need to find / remember all the place in the customizer it's used. Instead, if there were SASS files, I could update the $primary-color value and it would cascade. Mind you, I get it, I'd have to assign the $variables to the properties (as I would in the customizer), I get that :) But even that for me is easier than driling up and down and around in the customizer. Sometimes I get dizzy from that :)
Funny, this is similar to the discussion about headings and font sizes. Ultimately, I'm using the a layer of abstraction, which can add an extra layer - of confusion? - to the customizer. I think I saw something about a future color pallet feature. Maybe that'll help? But I think I'd still like to have the SASS, if it's avaiilable. Or even just all the CSS the customizer might render. I can reverse engineer the SASS from that, I hope :)
The text was updated successfully, but these errors were encountered: