Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Modernize color palette picker and better surface color personalization #42278

Open
richtabor opened this issue Jul 8, 2022 · 0 comments
Open
Labels
[Feature] Colors Color management Global Styles Anything related to the broader Global Styles efforts, including Styles Engine and theme.json Needs Design Feedback Needs general design feedback. Needs Design Needs design efforts. [Type] Enhancement A suggestion for improvement.

Comments

@richtabor
Copy link
Member

What problem does this address?

The color palette picker UI could use some cleaning up, and after auditing color interactions in Global Styles - I suspect there's a clever way to encourage color palette personalization/creation in-context, instead of requiring people to navigate away from editing towards Global Styles.

What is your proposed solution?

Modernizing the color palette picker UI:

Overall improving the layout of the component by shrinking the footprint, so that color select items do not leave empty space — but rather fill to the container. Also suggesting a tweak to the hover/active/focus state, to simplify those/introduce less weight to selection experience (but maintain visibility; perhaps improve).

CleanShot.2022-07-08.at.12.44.05.mp4

Better surfacing color personalization

Here's a rudimentary mockup of how this could work perhaps. If we lean into this model, we'll want to prototype how deleting would work, and how applying one-off colors would differ from selecting/editing any existing theme/custom colors.

CleanShot.2022-07-08.at.12.52.56.mp4

Notes

  1. I realize the Solid | Gradient toggle select is not in my prototype; that doesn't change the idea.
  2. This idea considers that there may not need to be a distinction between theme and custom colors — they could be "Site" colors. Technically speaking the distinction is fine (just as technically a theme's template parts and a user's templates parts are different), but experience wise I question if its necessary/useful. I explored this initially when auditing the Global Styles color edit flow here: https://github.com/WordPress/gutenberg/issues/422743.

Related

@richtabor richtabor added [Type] Enhancement A suggestion for improvement. Needs Design Feedback Needs general design feedback. Needs Design Needs design efforts. Global Styles Anything related to the broader Global Styles efforts, including Styles Engine and theme.json [Feature] Colors Color management labels Jul 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Feature] Colors Color management Global Styles Anything related to the broader Global Styles efforts, including Styles Engine and theme.json Needs Design Feedback Needs general design feedback. Needs Design Needs design efforts. [Type] Enhancement A suggestion for improvement.
Projects
None yet
Development

No branches or pull requests

1 participant