We Gave Our Free WordPress Plugins a Big Spring Cleanup

Sometimes plugin work feels less like coding and more like cleaning a giant workshop after a robot party.

That is what we just did at Devenia.

We cleaned up releases, fixed plugin docs, pushed missing updates, made sure ZIP files were packed properly, and then went back to our public plugin pages on devenia.com/plugins to make sure they finally matched reality.

In plain English: we took a bunch of plugin shelves that had the right boxes but the wrong labels, and we fixed the labels too.

What We Actually Did

  • Published missing releases for our own MCP plugins
  • Verified that release ZIP files matched the staged copies
  • Cleaned up readme.txt files so the WordPress packages looked proper
  • Normalized GitHub README.md files so the repos looked proper too
  • Created the missing GitHub repo for mcp-abilities-formidable
  • Fixed branch tracking and repo hygiene for a few lagging plugin repos
  • Updated the public Devenia plugin pages so they stopped saying old wrong things

The Fun Part: Making the Plugin Pages Tell the Truth Again

This part was especially satisfying.

Our public plugin pages were not completely broken. They were worse in a sneaky way: they were old.

That means visitors could read something that sounded nice, but was no longer fully true. Old plugin counts. Old claims. Old download links. Old descriptions.

So we fixed that.

  • The main Plugins page now uses current descriptions for MCP Expose Abilities and URL Change Lockdown.
  • The MCP Expose Abilities page now reflects the real release state: core 3.0.28, 13 released add-ons, and the current plugin matrix.
  • The URL Change Lockdown page now explains the real scope of the plugin: slug protection, not the older wider lock-everything story.
  • Old release links were replaced so people do not get sent to stale ZIPs.

Why This Matters

If a plugin page says the wrong thing, people make bad decisions.

Maybe they install the wrong version. Maybe they expect features that changed months ago. Maybe they think a plugin is smaller, weaker, or more confusing than it really is.

That is boring damage, but it is still damage.

We would rather have plain, correct pages than shiny pages with dusty facts.

The Plugin Stack Is Bigger Now

The MCP plugin ecosystem has grown a lot. The core plugin handles WordPress-native tasks, and the add-ons now cover things like Elementor, Rank Math, Wordfence, Cloudflare, Brevo, Formidable, WPML, filesystem work, Google Workspace, and more.

So part of this cleanup was simply making our public pages catch up with the actual work already sitting in GitHub releases.

Tiny Nerdy Victories We Also Enjoyed

  • Watching version numbers line up correctly
  • Seeing release assets match staged ZIP files exactly
  • Removing stale claims from plugin pages
  • Fixing a download link that still pointed at an ancient release
  • Turning messy repo state into clean repo state

What You Can Look At Now

The Short Version

We fixed the plugin boxes. Then we fixed the signs on the shelves. Now both parts match.

That is not the flashiest kind of work. But it is the kind that makes everything else less annoying.

And honestly, that is one of our favorite kinds of cleanup.

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.