Repository navigation
Add Patterns Team to the Make WordPress homepage teams list? #654
Description
The Make WordPress homepage currently lists contributor teams so users can discover where and how to contribute to the WordPress project.
Patterns is an active contribution area in the WordPress project. Contributors create, review, and improve patterns for the WordPress Pattern Directory, and the Patterns Team has also been represented at Contributor Day events.
However, I could not find a dedicated Patterns team entry on the Make WordPress homepage teams list.
Why this should be added
Adding the Patterns Team to the Make WordPress homepage would help:
Make Patterns' contribution more discoverable.
Give new contributors a clear entry point into pattern creation and review.
Highlight a beginner-friendly contribution path that does not always require coding.
Improve visibility for the WordPress Pattern Directory contribution workflow.
Align the Make WordPress homepage with current contribution activity around Patterns.
Suggested team card content
Patterns
The Patterns Team helps create, review, and improve block patterns for the WordPress Pattern Directory. Patterns are reusable combinations of blocks that help users build pages faster using the Block Editor. Contributors can help by creating new patterns, reviewing submissions for quality, accessibility, and design, and supporting first-time contributors.
Suggested link
https://wordpress.org/patterns/
Or, if there is/will be a dedicated Make Patterns blog, the card should link to that instead.
Acceptance criteria
Add a Patterns team card to the Make WordPress homepage teams list.
Include a short description explaining what the Patterns Team does.
Link the card to the most appropriate Patterns contribution destination.
Ensure the card follows the same layout and style as the existing team cards.
Additional context, then we are planning to make a monthly meeting for the #patterns team for now.
Patterns are a very approachable way for designers, site builders, developers, and Block Editor users to contribute to WordPress. Adding this team to Make WordPress would help more contributors discover this path.
Activity
sumitsinghwp commentedon May 26, 2026
Something like this :)
Patterns
Add a beautiful, ready-to-go layout to any WordPress site with a simple copy/paste.
dd32 commentedon May 27, 2026
The list of teams on the Make homepage are make.wordpress.org/**** teams, Sounds like we need to create a dedicated Patterns team with full make site and all tooling?
sumitsinghwp commentedon May 27, 2026
@dd32 i think https://wordpress.org/patterns/ is dedicated website for patterns team? I am not sure , but if we can make dedicated then great to manage and improved this team and expand #patterns things and connect more wo folks and focus on this amazing team too 😀.
@kafleg @supernovia can share your thoughts here please?
dd32 commentedon May 27, 2026
@sumitsinghwp No :) That's the Pattern Directory; Not a Make site.
sumitsinghwp commentedon May 27, 2026
Okay, got it, then maybe better to make a child separate site for patterns team
kafleg commentedon May 28, 2026
Patterns fall under themes, so I think we don't need a separate make team for patterns.
sumitsinghwp commentedon May 28, 2026
Okay, but what is plan if we need to expand Patterns team separately and connected more more wp folks in this amazing feature?
Also if you have another good plan to improve pattern team then let us know please @kafleg
supernovia commentedon May 28, 2026
So, here's what I'm seeing:
The Education team's perspective: Design students need a way to contribute, and patterns seems to be the most doable option right now. So they submit patterns for credits but don't hear back. They feel ignored, and if they get any feedback weeks later, it feels too generic to be actionable.
My initial thought: We must have a backlog or one overwhelmed reviewer. Let's find ways to add more reviewers.
Kafleg perspective: The issue isn't the review bottleneck - it's pattern quality and limited discoverability to patterns in the first place. He doesn't want help right now, and is concerned that new reviewers might approve patterns he would reject because they don't share his standards.
After a chat we thought we should:
Team or No team? Before we had a #patterns, questions went unanswered and bugs sat unfixed for months. Since creating the channel, we've solved bugs, drafted guidelines, and have active discussions. This suggests that having a dedicated, discoverable space helps.
However, creating make.wordpress.org/patterns won't solve the core issue if only one person can access submissions. I'm not even sure it would solve the problem if four people had access. We already have several defunct teams on make.wordpress.org - adding another team page without addressing that would just create one more abandoned space.
If I could wave a magic wand, we'd have:
Right now @kafleg has agreed to put the standards together, then we just figure out where to surface it. But we'd still need clear and consistent feedback when submissions don't meet standards, and that is a lot for one person to carry.
cc @peiraisotta
ajmaurya99 commentedon May 28, 2026
I'm supportive of the underlying goal of making Patterns contribution more discoverable and beginner-friendly. I'd like to add a few thoughts on what I think would help contributors the most.
Clearer guidelines / best practices. Having a single reviewer approving patterns is fine for now — that's not really the bottleneck. The bigger gap is that first-time contributors don't have a clear reference for what's expected, and in particular there's no documented way to understand what can cause a pattern to be rejected. A short, referenceable set of best practices and common rejection reasons would help newcomers submit with more confidence and make reviews more consistent.
No feedback loop on submissions. Right now the outcome is effectively binary — accept or reject — and a declined contributor usually has no idea why. That's discouraging for exactly the first-timers we're trying to attract. There should be some way to give feedback on a submission rather than just rejecting it, even something as simple as a short reason attached to a decline.
On the team page itself. If the priority is discoverability, clearer guidelines and a feedback mechanism may serve newcomers better — so we could hold off on adding the Patterns Team to the main landing page for now. Once the monthly #patterns meeting is running consistently, a team presence would have something real to point people to.
cc - @supernovia @sumitsinghwp
joedolson commentedon Jun 2, 2026
An issue I've recently started to address for accessibility issues is what we can do to report issues with WordPress.org authored patterns (https://wordpress.org/patterns/author/wordpressdotorg/) that have accessibility issues. Right now I have no idea who to talk to about making any changes to that; the authors are obscured and with no patterns team, I don't have any idea who to talk to about getting changes made.