Over the last few weeks, I’ve been working on making the WordPress Plugin 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.org access. This has been worked on in #555.
Getting started
The easiest way to get started is to clone the GitHub 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 startOn first start, around 30 plugins are automatically imported from WordPress.org across the featured, popular, and beta 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 core functionality, a number of closed-source and otherwise private tooling and scripts are used here) - Test the readme validator and block 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 SVN 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.