-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Improve UX of template inspector "transform into" experience #59448
Comments
A simple way to resolve the first and second points could be to include an option in the list, initially selected, based on the current template structure. It's tricky though, because if you swapped, saved and reloaded, then the 'old' structure would vanish. Perhaps we could prompt the user to save or discard the old design as a custom pattern in multi-entity saving? |
This is rather similar to how style variations can easily be lost, and this issue on how to save style variations might be relevant: #45371 That said, my instinct would also go in this direction: show the current one as a "Current" (including the italic that emphasizes it being ephemeral). Besides, undo still works, no? |
Yes, and other presets like Typography and Color. We should definitely seek to align the UX around these tasks, especially as they will be more prominent in the upcoming zoomed-out / section work. |
The problem is that there is no connection between the pattern in the canvas and the patterns in the inspector, so these are things we don't know. I think the work we are doing on using patterns on sections could help with this. |
Using the patterns surfaced in the template inspector, I've noticed a few oddities:
Google.Chrome.mp4
@WordPress/gutenberg-design for more feedback. Wanted to share early as this was just merged for 17.8 (tested this with 17.8RC4). @scruffian since you implemented this.
The text was updated successfully, but these errors were encountered: