-
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
Improvements for Quick Inserter prioritizing patterns #40117
Comments
Hi @annezazu,
This is already happening if one searches for a block one can insert a block: Is this behavior not working as expected in your tests? |
Regarding "Consider updating the + button to have it show as "add pattern" when it's prioritizing patterns." I opened a PR to do that thank you for catching this issue 👍 For "Consider adding in some sort of intro text to the Quick Inserter panel to clarify that these are patterns one is looking at." I think we would need some design help, maybe @jameskoster or @jasmussen have some insights? |
Perhaps we can make it more obvious by optimising the dimensions for patterns. At the moment the previews aren't all that helpful because they're so small. I don't know if that means switching to a single column, or making the popover larger. There's some work to be done around which patterns we surface too. In template editing, the patterns should be contextual to the current template. Also, does it make sense to expose header and footer patterns so prominently if the current template already includes a header and footer? I hope these are the sort of things that will make this feature feel more useful. |
Note another improvement regarding prioritizing patterns could be related to - #41397. Since right now prioritizing patterns over blocks when searching for template part variations like "header" results in options that just add blocks directly to the template, bypassing all the features provided by the template parts these patterns are expected to be contained in. |
I would prefer to have the same experience each time. It’s confusing to suddenly see patterns when I was expecting blocks. Or even better, there could be a choice to set it to one or the other, just as we can change other editor settings (full screen, code vs. visual) |
Different order of pattern and blocks in site- and post-editor reported as WCAG violation: |
Perhaps the upcoming pattern-centric building experience (#50739) makes this feature (prioritising patterns in the quick inserter) defunct? |
Yes, I agree. What are the conditions to get patterns in the Quick Inserter? I think the Quick Inserter should always be the same experience, surfacing blocks with "Browse all" opening the Inserter. |
Perhaps we should reframe this issue in that direction. What do you think @annezazu ? |
I'm having a hard time understanding what direction is being referenced here for some reason.
What does this mean exactly? What's "the same experience" in this case? I'm guessing that means removing the work to surface patterns contextually but want to be sure. Ultimately, game to shape this in whatever way makes the most sense to designers because I agree. It remains very frustrating not be able to just add a block when patterns are prioritized. |
Yes, keep the quick inserter surfacing blocks with "Browse all" always opening the Inserter with the Blocks tab selected. That way when you press the blue + inserter within the standard editing experience, it performs the same actions. |
What problem does this address?
Currently, the Quick Inserter prioritizes showing patterns in a few situations thanks to the work done in #38709:
However, there are a few rough points:
What is your proposed solution?
I think there should be a few enhancements, pending design thought:
cc @jorgefilipecosta
The text was updated successfully, but these errors were encountered: