Patterns: iterate on experience of registering patterns from pattern directory for themers #55109
Labels
[Feature] Pattern Directory
The Pattern Directory, a place to find patterns
[Feature] Patterns
A collection of blocks that can be synced (previously reusable blocks) or unsynced
[Feature] Themes
Questions or issues with incorporating or styling blocks in a theme.
Needs Design Feedback
Needs general design feedback.
Needs Technical Feedback
Needs testing from a developer perspective.
[Type] Enhancement
A suggestion for improvement.
With block themes increasing and patterns continuing to play an important role, I want to return to the efforts to allow for patterns to be registered from the pattern directory via theme.json in #38323.
In that PR, a discussion was had around categories since there is no parity between pattern directory categories and core categories. Without going into iterating on pattern categories #47847, I wanted to open an issue around the experience of registering patterns from the pattern directory for themes, how we can filter those patterns, and the expected experience for categorizing these patterns. A few points:
Here's a quick video showing some of this:
pattern.experience.register.themejson.mov
Ideally, theme authors could use the pattern directory as a main way to reference patterns (which would benefit the larger ecosystem with more patterns to pull from) and even reuse across different themes if they wanted. Before doing this though, these kinks needed to be sorted out, particularly with controlling categorization and filtering. Is there a way we could auto add a category or register a new category for patterns registered for a theme in this way? This was briefly discussed in the original PR #38323 (comment)
This also touches on this broader issue of having a "theme source" for patterns in the pattern directory which I could imagine would make the experience more tightly coupled and clear WordPress/pattern-directory#573
cc @WordPress/block-themers for more insights and feedback :)
The text was updated successfully, but these errors were encountered: