Dion Hulse 5:21 am on March 16, 2026  

Plugin Directory: Local Development Environment

Over the last few weeks, I’ve been working on making the WordPress PluginPlugin 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. Directory available as a local development environment. I’m happy to announce that we now have a wp-env-based setup that lets anyone contribute to and test enhancements (and fixing bugs!) in the Plugin Directory, without needing any special WordPress.orgWordPress.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/ access. This has been worked on in #555.

Getting started

The easiest way to get started is to clone the GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. https://github.com/ mirror, and boot the environment up:

git clone https://github.com/WordPress/wordpress.org.git
cd wordpress.org/environments
npm install
npm run plugins:env start

On first start, around 30 plugins are automatically imported from WordPress.org across the featured, popular, and betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. sections.

For more information, have a read of the documentation: https://github.com/WordPress/wordpress.org/tree/trunk/environments

What you can do locally

  • Browse plugin pages, sections (featured, popular, beta, new, updated), and search
  • Submit plugins and walk through the review/approval process
    (This is limited to coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. functionality, a number of closed-source and otherwise private tooling and scripts are used here)
  • Test the readme validator and 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. plugin checker
  • Import any plugin from WordPress.org by slug: npm run plugins:import -- hello-dolly

Known limitations

Some features that rely on production-only infrastructure are not available locally, such as SVNSVN Apache Subversion (often abbreviated SVN, after its command name svn) is a software versioning and revision control system. Software developers use Subversion to maintain current and historical versions of files such as source code, web pages, and documentation. Its goal is to be a mostly compatible successor to the widely used Concurrent Versions System (CVS). WordPress core and the wordpress.org released code are all centrally managed through SVN. https://subversion.apache.org/. sync, HelpScout integration, and complete plugin reviews.

The Search functionality is also using WordPress’ builtin search, not the ElasticSearch-powered index we use on WordPress.org.

Feedback

If you run into issues or have suggestions, please file a ticket on Meta Trac with the Plugin Directory component.

+make.wordpress.org/plugins/