WordPress / WordPress/pattern-directory

Surface clear submission guidelines in advance

Open
#751 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
PHP
Stars
134
Forks
46
Avg merge
9h 4m
Merged PRs (30d)
19

Description

Patterns reviewers have complained that they're getting poor-quality submissions, but it's currently difficult to find expected quality standards until after one designs a pattern and clicks submit.

Current flow:

  • They're invited to create a pattern
  • On submit they're asked to check the guidelines
  • Clicking that asks if they want to leave the site and lose their work :/

It would be kinder to set standards in advance, maybe a modal when they open the new pattern editor, or at least brief guides and a link to more info.

Here's one page with some vague rules. It's a start:
https://wordpress.org/patterns/

Or we could point to the patterns submission pathway:
https://make.wordpress.org/handbook/pathways/design/submit-block-patterns/

https://github.com/user-attachments/assets/d8ae453b-f517-4809-87cb-4d1c7bba9a78

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the new pattern editor flow described in the issue, especially where users are invited to create a pattern and where submission guidelines are shown. Review the linked WordPress guidance for the expected standards. Done means contributors see clear guidance before designing or submitting and are not forced to leave the site and lose their work.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.