-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Site Editor Inserter(s): Prioritise Template Parts over Patterns, and indicate the difference between the two #42501
Comments
I can see merit in both the icon indicators and the separate sections. I'd lean toward separation because template parts and patterns are functionally different so a more obvious separation might be helpful. I also think that, in most cases, parts would be used more frequently in the site editor than patterns. |
I would prefer the icon because I feel a bit overwhelmed by the size of the inserter in the example. |
I don't have a strong opinion, but do lean slightly towards the separation approach purely because it is consistent with other UIs that present the same content. We can explore how we might improve the experience holistically as a dedicated effort, rather than having several of different versions of essentially the same thing across the editor. |
Where did we end up with this? |
Seems we're looking for consensus on how to present everything. These are the options we have atm: Now that I think of it, another option would be: Clicking the root-level inserter engages the zoomed-out view with the main Inserter panel open. The separation of template parts / patterns is handled therein. |
I'm not seeing the pattern/part preview within the quick inserter any more - is this issue still relevant @jameskoster |
The quick inserter currently surfaces patterns, both by default and when you search:
But it's not always clear whether the options (like in the screenshot above) are template parts or patterns, which can lead to folks mistakenly inserting a pattern where a template part would be preferable.
This issue can be partially fixed by #41397, but it might be best to establish some visual distinction to cover cases where patterns and template parts share a name. There are a couple ways to do this, one solution would be to simply list them separately:
This would be similar to what you find in the current implementation of the template part replacement modal:
Another option would be to list them together but use the template part icon to distinguish between patterns and things like headers / footers. Rough example:
The text was updated successfully, but these errors were encountered: