WordPress Help

Official documentation, learning resources, and contributor guides collected from WordPress.org.

  • About

    The WordPress training team helps people learn to use, extend, and contribute to WordPress through synchronous and asynchronous learning, as well as downloadable lesson plans for instructors to use in live environments, available at learn.wordpress.org. Learn WordPress makes WordPress knowledge accessible to all by empowering individuals worldwide to create, contribute, and grow within the WordPress…

    Read guide

  • Glossary

    dl.glossary-list dd { margin-top: -50px; padding-top: 50px; } Admin P2 A plugin administrator private make blog for managing security and legal issues not possible to disclose publicly at this time. # FUD Fear, uncertainty and doubt, usually evoked intentionally in order to put a competitor at a disadvantage. # Help Scout A 3rd party service…

    Read guide

  • WordPress Hosting Team Handbook

    Welcome to the WordPress Hosting Handbook! Here you will find WordPress hosting best practice documentation developed collaboratively by the Hosting Team. Use the “Contents” menu on the left to navigate topics. About the Hosting Team The WordPress Hosting Team consists of experienced professionals dedicated to bridging the gap between WordPress and hosting environments. Our members…

    Read guide

  • Using the Review Admin Tool

    Reviews are done via the Dashboard on the directory. Only reviewers and admins have access to this. Important Links Review Checklist Review Walkthrough All new plugins have a status of ‘draft’. This means they have not yet been reviewed. To view all newly submitted plugins, go to My Plugins and click on Pending Initial Review:…

    Read guide

  • Directory Maintenance

    Maintaining the directory can be a full-time job. To achieve this, we rely on multiple tools to constantly scan, review, and monitor check-ins. There are some filters on SVN that prevent dangerous code from being committed to the repositories, the rest of the work is done by scanning. Removing Plugins Plugins are removed for reasons…

    Read guide

  • Security and Guideline Violation Reports

    Users, security firms, and developers all send in security reports. Each one must be read, reviewed, and replied to without exception. The goal is to ensure accuracy in reporting and communicate clearly to the developers what must be corrected and why. While all plugins in the WordPress.org Plugin Directory are required to be compatible with…

    Read guide

  • 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…

    Read guide

  • 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…

    Read guide

  • 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…

    Read guide

  • 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…

    Read guide