-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Shadow: create / edit shadows in the global styles #57100
Comments
@jasmussen @richtabor I have following thoughts on the editing experience for the shadows. Current state: From the conversation here, the new UI should have options to create or edit a shadow, but it is not clear where this new UI belong. Are you suggesting to make the same panel (as above) editable, or make it a separate component? Please share your thoughts. |
I think @jameskoster or @SaxonF may have had a hand in some of those more recent shadow design tools (which look promising!) so I'd appreciate their input. That said, I don't see global styles having a top level item called Shadows. There may be an aditional space for the increasing amount of controls that don't fit in Typography, Colors, and Layout. But how to structure that may be best informed by #47369. |
I could potentially see an 'Effects' section where you're able to manage shadows, filters, duotone, and similar styles. Though I would agree that preset management in global styles needs some general design attention. |
I think "Effects" was recently suggested by @richtabor for something similar, but not sure if that's the right word either. Worst case, could be Shadow & Border to match the panel. |
Created #60706 to explore the ideas around shadows editing experience. It is inspired from color palette and addresses the following.
Following is the initial UIEditing experience of default/theme shadows. Editing experience of custom shadows. Problems / QuestionsSince a shadow can be a combination of individual shadow strings (ex: value for default preset Should this panel have tab layout within, each tab for one sub shadow? I am sure it is not the best ideas and not implemented in the draft PR. It picks, only the first part of the shadow for now. Also, this initial exploration doesn't include a @WordPress/gutenberg-design @richtabor Please suggest UI for the complete workflow. |
Nice work so far, it's exciting to see progress on this. The thing that stands out most here is the preview UI, this one: Both in the block inspector, and in global styles, it doesn't work very well imo. In the block editing context, you can see a better, more accurate preview on the canvas, and in global styles they are not interactive, so we could go ahead and show the itemgroup UI, this one:
For this feature to scale, and for us not to have to redesign it in the near-term, this detail feels important to me. Here's a mockup of how adding / editing a custom shadow could work: custom.shadow.mp4Figma prototype to click through.
What do y'all think? A couple of small details I noticed in the PR:
|
@jameskoster Thanks for the designs. They look great and addressing all the issues. I have a question on color selection. How would you propose the color selection in the following design? I assume it would be the similar experience such as text color selection panel. Can you confirm?
Sorry that I did not give attention to the detailed styles in the first iteration as I was aiming to bring up something quickly. These issues should be addressed along with the proposed designs. |
That's correct, yes. The UI should be the same :) |
@jameskoster New design looks great. I have taken part of it in the first iteration. |
What problem does this address?
This is a sub task of #44651
With current implementation (in #44651), plugin gives four preset shadows and user can add more presets using
theme.json
and they appear in the global styles and site editor.As a next step, add ability to edit or to create a shadow from the editor.
What is your proposed solution?
Following is the suggested design.
custom.shadow.mp4
Find more discussion related to this here
The text was updated successfully, but these errors were encountered: