Content type: Handbook

  • Review Walkthrough

    The following is a walkthrough of reviewing a plugin. Warning: This page does not include every aspect of a review yet and should be considered highly work in progress. The User Before reviewing the plugin itself, ensure the user is not currently prohibited from submitting new plugins, or attempting to evade restrictions due to a…

  • Review Checklist

    Reviewer Workflow Verify the submitted name and subject matter are acceptable. Download the ZIP. Check all files for guideline violations. Ensure the readme is clear (only a requirement for services). Test in a secure environment. Detail any issues found and email the developer from HelpScout. If no issues are found, approve the plugin. Required All…

  • Performing Reviews

    Overview The bulk of the work done by the review team is actually reviewing new plugins. The steps taken to review a new plugin are actually the same as those for reviewing any existing plugin. The goal is to look for as much ‘wrong’ as possible, identify it clearly, and communicate that back to the…

  • Expectations

    Introduction All members of the plugin team are held to an exceptionally high standard, not just in their ability to process code for security, but also in the way they handle security issues, ethical/behavioral situations, and privileged information. While everyone makes mistakes, the strength of the plugin team comes from not just our appearance of…

  • Get Involved

    Intro Everyone is encouraged to join Slack and follow the public blog to participate in any discussions there. Report Plugins Read Reporting Plugin Security Issues for more information. Whether or not you are a plugin reviewer, everyone is welcome to report plugins with security issues or ones that violate the plugin guidelines to the team.…

  • The Team

    The Plugin Review Team is a group of volunteers who review and approve plugins newly submitted to be hosted on the official WordPress.org Plugin Directory. The team maintains the Plugin Reviewer Handbook and the official tools for reviewing plugins. The team also is responsible for investigating guideline infringements and behavioral issues surrounding plugins and developers…

  • Team P2

    On your Rosetta site, you have a “Team P2” blog for your locale team to collaborate, located at LOCALE.wordpress.org/team. Here are some examples of the Team P2: https://fr.wordpress.org/team/ https://ja.wordpress.org/team/ https://es.wordpress.org/team/ If you don’t find a Team P2 on your Rosetta site, talk with one of the Polyglots Global Mentors. You can use this for whatever…

  • Adding locale team site

    This is the process the Polyglots Leadership team uses to create new locale team site on requests by users. To request a new team site, please post a request on https://make.wordpress.org/polyglots. Add new Team O2 To create a new Team O2 go to: The Global Site Network > Add New Enter the associated subdomain of…

  • Adding locale support forums (with HelpHub)

    This is the process the Polyglots Leadership team uses to create new locale forums on requests by users. To request a new forum, please post a request on https://make.wordpress.org/polyglots (examples). Add New Forums To create a new forum go to: The Global Site Network > Add New Enter the associated subdomain of the locale in the URL…

  • Plugin Directory Reviewer’s Handbook

    Welcome to the Plugin Directory Reviewer’s Handbook, the place to learn how to review WordPress plugins. This handbook will provide the information you need to get started as a new reviewer, or remind you of best practices. Here you can learn about how the WordPress project is organized, communication channels, best practices, the workflow process,…