WordPress / WordPress/pattern-directory
Improve connection between theme and pattern directories
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 134
- Forks
- 46
- Avg merge
- 9h 4m
- Merged PRs (30d)
- 19
Description
Right now, when viewing block themes, the patterns within the theme are visible. However, the opposite isn't true when you're browsing the pattern directory. This issue seeks to propose that we better connect these experiences to create a more cohesive experience, lay the ground work for more granular theme switching, and improve the discoverability of the work of theme authors.
Tied to this, it means there's a potential for when someone is submitting a block theme, that they could automatically include patterns in the pattern directory that are tied to what they are submitting.
cc @WordPress/block-themers for thoughts here!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing how block themes and patterns are browsed, and how block themes are submitted to the directory. Define the intended connection between these experiences, including whether theme submissions should automatically expose associated patterns; completion requires an agreed product design and implementation scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php, wordpress
- Domain
- content, design, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100