Make pattern modal views more consistent

[richtabor]

What problem does this address?

Now that we have a number of pattern experiences within core, we should consider where there are inconsistencies that can be brought closer together. I've outlined the three pattern modal experiences from a block selection (__experimentalBlockPatternSetup), add new page, and pattern explorer:

From the Query loop block's pattern selector:

From the new 6.0 core/post-content Add new modal:

( I just added two random patterns to the blockType, so we could see these here)

From the Pattern Explorer:

What is your proposed solution?

1. Remove single-view from __experimentalBlockPatternSetup

Take the block pattern selector (__experimentalBlockPatternSetup) and make it back to a grid view (not the current single pattern view). Consider even removing the single view entirely (not sure how helpful that is).

2. Make pattern modal UI consistent

Make the modal UI consistent across all three experiences (width, columns, modal headers, etc).

3. Possibly add another level of categorization for blockTypes

Consider adding a sub-categorization layer to blockTypes, which could be very similar to the current Pattern Explorer UI does (sidebar with search + category)). This would be particularly useful for the "Add new" pattern view, where I could select the type of page to add, instead of seeing an uncategorized list of page patterns.

This could also be interesting for the Query block's __experimentalBlockPatternSetup use case as well, where the query patterns could be categorized by column count, featured images, grid, etc. (If this is interesting, we should probably spin up another issue relative to this).

Thoughts? 🤔

[annezazu]

Thanks for opening this up @richtabor! At a glance, this seems wildly similar to this issue: #39308 Mind consolidating feedback there and perhaps closing this one out instead?

[richtabor]

Good catch, will do.