Since my last post, I’ve been doing some thinking and digging into taxonomies on the plugin directory. There were a few common complaints about rethinking “tags” in the plugin directory. They boiled down to a few specific points: I need to mark my plugin as built for [plugin name]. I need to note which WordPress features my plugin supports. Tag pages are currently well-placed in search engine results and changing or removing them could lower my ranking. As a result of the above, among other things, three is not enough. This post will walk through a bit more detail on our thinking and address those points. The plugin directory was created to showcase free and open source plugins from all over, bringing them together to make it easier for WordPress users to customize their WordPress installations. As its grown to over 40,000 plugins, it’s gotten harder and harder for users to find the Right Plugin. While initially helpful, tags have become a free-for-all to indicate an assortment of things. Going forward, we’d like to re-focus our taxonomies to make it easier for users to find quality plugins. In an ideal world, a plugin’s readme would detail all of
Share This

We are using cookies on our website

Please confirm, if you accept our tracking cookies. You can also decline the tracking, so you can continue to visit our website without any data sent to third party services.