From Publishing Tool to Publishing Workspace
What began as a way to simplify WordPress.org SVN publishing gradually became something much larger: a complete release workspace for WordPress plugin developers.
WordPress Plugin Publisher brings the pieces of a release together into one native macOS application.
Create and validate a release. Connect its repositories. Prepare WordPress.org. Publish through SVN. Maintain GitHub. Update documentation and changelogs. Create versioned releases and tags. Verify what happened. And keep a history of what you’ve shipped.
Instead of remembering a long sequence of commands and manual steps, Publisher turns the process into a clear workflow.
.
About WordPress Plugin Publisher How it Began
Built because publishing a plugin shouldn’t be harder than building one.
WordPress Plugin Publisher began with a simple challenge.
We had created four WordPress plugins and needed a faster, easier way to publish and maintain them on WordPress.org and GitHub.
Building the plugins was only part of the work. Every release brought another sequence of tasks: creating the distribution ZIP, updating version information, preparing the WordPress.org SVN repository, managing trunk and tags, preserving directory artwork, handling credentials, updating GitHub, maintaining the README and changelog, creating releases, and making sure everything had actually published correctly.
For one plugin, that process was manageable.
For four, it became clear there had to be a better way.
So we built one.
Publishing Intelligence
One of the ideas at the heart of Publisher is simple:
You should know when a plugin is ready to publish.
Publishing Intelligence examines the release and its publishing environment and surfaces what is ready, what still needs attention, and what should happen next.
When Publisher says 100% — Ready to Publish, that confidence comes from understanding the pieces required for the release—not simply from enabling a button.
WordPress.org Without the SVN Headaches
WordPress.org remains an extraordinary home for plugins, but publishing through SVN can feel disconnected from the way modern software is developed.
Publisher bridges that gap.
It handles the mechanics of preparing WordPress.org repositories, updating trunk, creating version tags, preserving or replacing directory artwork, working with credentials, publishing changes, and verifying the resulting release.
The easiest way to publish your plugins to WordPress.org — without wrestling with SVN
Instead of remembering a long sequence of commands and manual steps, Publisher turns the process into a clear workflow.
.
SVN WordPress.org + GitHub
We also wanted Publisher to reflect how plugins are actually developed today.
WordPress.org and GitHub serve different purposes, so Publisher gives each its own dedicated publishing workflow rather than forcing them into one process.
A plugin can be prepared and published to WordPress.org while its GitHub repository is independently maintained with version information, README updates, changelog entries, commits, tags, and releases.
Two publishing destinations. One application.
SVN Built From Real Releases
Publisher wasn’t designed around a hypothetical release process.
It grew while we were actively building, submitting, updating, and publishing WordPress plugins ourselves.
Every unnecessary step became something to simplify. Every repeated task became a candidate for automation. Every point where a release could go wrong became an opportunity for validation.
That continues to guide the development of Publisher today.
The goal isn’t to hide what is happening.
It’s to make a sophisticated publishing process clear, dependable, and remarkably easy to use.
Made for People Who Build.
There is something special about finishing a piece of software and sending it out into the world.
The final steps shouldn’t be the part you dread.
WordPress Plugin Publisher exists so developers can spend more of their time creating great plugins—and less of it managing the machinery required to release them.
Build the plugin.
Let Publisher handle the release.