There are more than 60,000 plugins on WordPress.org plugin directory.
That’s not just a number. It’s one of the most important assets in the entire web ecosystem.
Each plugin represents:
- A solved problem
- A developer’s time and thinking
- A real-world use case, battle-tested
And crucially, they’re open source.
Meaning anyone can download them, study them, change them, improve them, remix them.
The missed opportunity
In theory, this is already possible.
In practice, it’s… not how things actually work.
Today, plugin remixing tends to happen in places like:
- GitHub
- GitLab
- Bitbucket
Or inside agencies, private repos, or local environments where tweaks get made quietly and never shared.
So instead of:
- remixing being visible
- improvements compounding
- ideas building on each other
We get:
- forks that disappear
- duplicated effort
- innovation happening in silos
The raw material is there. The system around it isn’t.
What if remixing was the feature?
Now imagine this:
You’re browsing a plugin on WordPress.org.
Next to “Download” is a new button:
Remix with AI
You click it.
Behind the scenes:
- The plugin is loaded into something like WordPress Playground
- An AI assistant understands the plugin’s structure
- You describe what you want:
“Make this work with WooCommerce subscriptions”
“Simplify the UI for non-technical users”
“Turn this into a front-end editor”
The AI makes the changes.
You test it instantly.
Then, with one click:
Publish as Remix
A new layer in the plugin directory
Now imagine every plugin page had a new section:
Remixes
- “Simplified version for charities”
- “Enterprise-safe version with locked UI”
- “Headless-ready version”
- “AI-powered version with automation built in”
Not forks hidden on GitHub.
Not abandoned experiments.
But visible, discoverable, usable remixes sitting alongside the original.
Like:
- Themes → Child themes
- Code → Variations
- Music → Remixes
What would this unlock?
1. Non-technical creators become builders
Right now, modifying a plugin requires:
- PHP knowledge
- WordPress internals
- Confidence not to break things
With AI + remixing:
- You describe what you want
- The system handles the complexity
Suddenly:
- marketers
- designers
- educators
- agencies
…can all create custom tools without writing code.
2. Real democratisation of app development
We talk a lot about “democratising publishing.”
This would be something bigger:
Democratising software creation.
Because instead of starting from scratch, you start from:
- a working plugin
- a proven idea
- a real user base
And build from there.
3. Compounding innovation
Right now, innovation is fragmented.
With remixing:
- Improvements stack
- Ideas evolve in public
- The best versions rise naturally
One plugin becomes:
- 10 variations
- then 100
- then entire ecosystems of specialised tools
4. A new growth loop for WordPress
Think about what this does strategically.
More remixing →
More experimentation →
More niche solutions →
More reasons to use WordPress →
More developers contributing →
More plugins improving →
It becomes a self-reinforcing system.
And importantly:
- All happening inside WordPress.org
- Not leaking out to other platforms
Leaning into what makes WordPress unique
There are a lot of new tools emerging.
AI-first builders.
Closed ecosystems.
“Start from scratch” platforms.
WordPress doesn’t win by copying them.
It wins by leaning into what it already has:
- 20+ years of shared effort
- A massive open ecosystem
- Tens of thousands of real solutions
- A global community of developers
That’s not easy to replicate.
It’s not even easy to understand from the outside.
But it’s powerful.
The role of plugin developers
This doesn’t replace plugin developers.
It amplifies them.
Because:
- Their work becomes the foundation for thousands of variations
- Their ideas spread further
- Their influence grows
And potentially:
- New monetisation models emerge
- Attribution becomes part of remix chains
- Reputation compounds across variations
The bigger idea
This isn’t just about plugins.
It’s about a shift in how software evolves.
From:
- isolated products
To:
- living systems
From:
- static releases
To:
- continuous remixing
From:
- “build from scratch”
To:
- “build from what already exists”
So… what if?
What if WordPress.org made remixing:
- visible
- easy
- AI-assisted
- native to the platform
What if every plugin wasn’t just an endpoint…
but a starting point?
Because if that happens, WordPress stops being:
- just a CMS
- just a website builder
And starts becoming something else entirely:
A platform where software evolves in public.
Leave a Reply