Plugin Directory

The long-awaited official WordPress plugin directory is now live. Matt has the announcement post.

Most of my work on the project was behind-the-scenes stuff that Michael Adams assembled and Matt Thomas made shiny, so the end result was a pleasant surprise for me. Nice work, guys!

The directory acts as a front-end to The main conduit connecting the two is the readme.txt format that evolved on the wp-hackers mailing list and with discussions between Matt Mullenweg, Michael Adams and me. The format is quasi-Markdown. The main sections are fully parsed with Markdown, but the headings themselves are a bit different and there is a section at the top for meta information that is proprietary. But the goal is the same as with Markdown: human readability. The readme.txt files should look nice and elegant to people who are reading them in a text editor, and they should be translated into nice semantic HTML versions for the plugin directory. Here’s the readme.txt for my Subscribe to Comments plugin. And here is the result of that file, parsed into the plugin directory.

This is only round one… the dangling of a carrot in front of plugin developers, trying to convince them to update their plugins with nice readme.txt files. The real exciting step is connecting WordPress to the plugin directory, which will allow for plugin update notification. I’d also like to see the directory interface with Trac somehow so that users can report and track bugs in plugins. Stay tuned!

28 thoughts on “Plugin Directory

  1. you don’t really mean proprietary, just mean “wordpress specific”, right?

    alex mentioned a readme validator a while back, does that still exist?

  2. This is a good development Mark. What happened to the old plugins in
    I haven’t updated my plugins tehre in a while… but keen to make all the changes necessary… any suggestions?

  3. The plugins directory is the online equivalent of a huge toychest with new toys continuously added in.

    It’s a lot of fun to explore how far WP can go, using combinations of the available plugins!

  4. Pingback: track bugs

Comments are closed.