Building with Patterns

[mtias]

This issue will track and describe a few projects around making patterns a more central part of the experience of creating templates and pages.

Inserter

• Pattern Inserter: Next #41379
• Surface related patterns in the template inspector #44582.

Creation

This is about discovery and the user experience of starting with blank or partially blank templates, the role of semantic template parts as containers, etc.

• The wp:pattern block #48458. 💎
• Patterns as Sectioning Elements #39281.
• Connecting patterns with specific contexts & transforms #27575.
• Shuffle content blocks when templateLock is contentOnly #44581.
• Template editing: convert semantic patterns to template parts upon insertion #41397. ⚠️
• Prioritize patterns on quick inserter instead of blocks at the root of templates #36697.
• Semantic Patterns #28737.
• Display block pattern options in a modal rather than placeholder state #31033.
• Site Editing: Increase prominence of contextual patterns when template editing #28739.

Theme Registration and Directory

• Allow themes to surface specific patterns from the Patterns Directory #35364.
• Block Patterns: Automatically load headered files from a theme's /patterns directory #36751.

New Pages

• Block Patterns for page creation. #38787

[mtias]

I grouped some consideration that are being surfaced as we use patterns more as building tools into #39281 to try and address some of the main usability issues that are appearing.

[dugyen]

@mtias @annezazu
Is it possible to add those patterns available in wordpress.org to the themes's/patterns directory?

[dugyen]

It would help WordPress users to search directly from TT3 or Updated TT2 theme, not from WordPress.org

[annezazu]

@dugyen can you explain a bit more what you want to see? Feel free to DM me on slack (@annezazu on Make Slack) so we can talk out what you want and not detract from this issue. You are welcome to also open a new issue for this repo and tag me in it too :)