Proposal: Approving Block Pattern Directory Submissions

Welcome!

The WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:

Found a bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority.? Create a ticket in the bug tracker.

Want to contribute? Get started quickly with tickets marked as good first bugs for new contributors or join a bug scrub. There’s more on the reports page, like patches needing testing, and on feature projects page.

Other questions? Here is a detailed handbook for contributors, complete with tutorials.

Happy new year, everyone!

The BlockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. Pattern Directory will soon be live and ready to accept custom Block Pattern submissions! In anticipation of this new directory, questions have been raised around best practices for submitted Block Patterns.

To help encourage contributors to submit Block Patterns, I propose that some basic automated checks, along with spam filters, are implemented. These automated checks could be modeled after what the Plugins team has in place to avoid naming confusion, trademarks, etc. As long as a submitted Block Pattern passes these checks, it will be published immediately. Of course, if a Block Pattern passes the automated check, but includes inadvisable content (for example, an inappropriate image), it can be flagged for manual review.

If you have any concerns, questions, or thoughts about this proposal, please leave your thoughts in the comments by next Friday, January 14, 2022.

Evan Mullins 9:05 pm on January 7, 2022

I support this idea.

I was curious about implementation for flagging the pattern for manual review and went to look at the directory. I’m happy to report there is already a “Report this pattern” button in the directory.
- Angela Jin 2:23 pm on January 10, 2022
  
  Thanks for sharing, Evan!

Comments are closed.

Welcome!

Communication

Share this: