I pitched this to Matt directly and have been given the go ahead to pave the way here. This post begins that process and documents the Featured Plugins experiment currently underway on WordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/. The goal is to surface newer plugins in the directory that meet a defined quality bar but have limited visibility. Eight plugins are selected every two weeks.
Eligibility
To be considered, a plugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party. must meet all of the following baseline requirements:
Active installs: fewer than 10,000
Age: listed in the directory for 12 months or less
No open security vulnerabilities
Compatible with the current major release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope. of WordPress
Updated within the last 6 months
Selection Criteria
Plugins that pass the eligibility requirements are evaluated against three categories of criteria.
Technical standards
Code is human-readable and follows WordPress coding standards The Accessibility, PHP, JavaScript, CSS, HTML, etc. coding standards as published in the WordPress Coding Standards Handbook.
May also refer to The collection of PHP_CodeSniffer rules (sniffs) used to format and validate PHP code developed for WordPress according to the PHP coding standards.
Proper use of escaping, sanitization, and nonces
No unnecessary bundling of libraries or WordPress core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. functionality
Plugin readme accurately describes what the plugin does
Ecosystem fit
Addresses a problem not already well-served by existing plugins
Provides functionality with genuine utility to WordPress users
Developer engagement
Developer is responsive in the support forums
UX User experience reflects care and intentionality in the implementation
How Decisions Are Made
Plugin selection is currently handled by Nick Hamze. The process and governance around selections will be reassessed as the experiment develops.
How Plugins Are Considered
All plugins that meet the eligibility requirements are automatically included in the pool for consideration. No submission is required.
Plugin authors who want to provide additional context about their plugin — or make a case for its inclusion — can do so in the #featuredplugins channel on the Make WordPress Slack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.
Tracking Progress
This experiment is tracked openly. Feedback on the criteria, the process, or specific selections can be shared in the #featuredplugins Slack channel. The process and governance around selections will be reassessed as the experiment develops. Right now, the aim is to experiment first with a small scope to ensure it’s meaningful for end users, plugin authors, and contributors. As the work evolves, more documentation and any necessary process can be added so future contributors can join.