I’ll be the first to admit that I think the WordPress Plugin Repository does some great things for WordPress and for its user base. When they rolled out the updated forums and the some of the new features, I was really excited about it.
But as time has passed, I’ve come to believe that the repository is more user-centric than developer-centric. Don’t read me wrong: I’m not claiming that this is an either/or situation. Ideally, both should be elevated to the same level.
On one hand, this makes perfect sense. After all, you have thousands of plugins all of which are available for users to search and download not only from the web, but from within the WordPress dashboard.
But plugins are created by developers – often times for free, obviously – but I don’t think that the repository does such a good job of supporting the work of the developers.
Sure, I agree that free hosting of your plugins is great and the ability to generate a landing page with several rich features based solely on a README is impressive, but each of these things also results in a number of issues that simply make it difficult to stay motivated to continue contributing plugins to the economy.
All that to say, I think the repository is a fantastic resource where users are the first class citizens. To that point, I want to outline several issues that I’ve experienced while using the WordPress plugins repository as a developer.
And for those of you who have read this blog, you know that I dislike when people offer problems without proposed solutions, so I’m aiming to provide those, as well.
Continue reading