Try and place patterns in default categories instead of declaring our own

[kjellr]

Currently, Twenty Twenty-Two declares five new pattern categories:

• Twenty Twenty-Two General
• Twenty Twenty-Two Footers
• Twenty Twenty-Two Headers
• Twenty Twenty-Two Posts
• Twenty Twenty-Two Pages

Most of these categories should/will/do exist in Gutenberg by default, and it would be great if we could hook into them automatically rather than declare our own duplicate, lengthy category names.

For example, it would be ideal if we could just place our theme header patterns in the normal "Headers" category, and have them show up before the default set.

Screenshot

[shaunandrews]

I've seen it mentioned a few times that perhaps we should group these categories by the way their created; Having a "Twenty Twenty-Two" section or a "Coblocks" section, but this still leads to having duplicate categories like in the mockup below:

it would be ideal if we could just place our theme header patterns in the normal "Headers" category, and have them show up before the default set.

Agreed 100%. I think we can even go a little further and highlight the theme-recommended patterns at the top of the grid:

Then, the sidebar can show an item for the theme's patterns along with items any plugin provided patterns — this avoids having duplicated categories, and keeps the list clean.

[ndiego]

I have some ideas how this all could functionally work. Will work on getting that more formalized this week.

[kjellr]

I took a stab at adding these to the default categories in the theme itself. A couple observations:

• I was able to get the Query patterns added to the default "Query" category, as established in Gutenberg just fine. But honestly, I think that category name is really confusing for users. We should probably change it to "Posts" here, and try to get Gutenberg to follow suit.
• I'm unable to place items in the "Headers" category. I imagine that is because it comes from the pattern directory. @ryelle do you happen to know if it's possible for a theme to override that? Our goal would be to take the patterns that are defined here in the theme, and place them in the pre-existing "Headers" category in the editor.

[ryelle]

"Headers" is a core category, so it should work- the slug is header, though. Other than that, the approach in #284 looks good to me.

[kjellr]

Ha, thank you for catching that! I'll give it a try. 🙌