Per Ola is currently working as CTO in mBricks (www.mbricks.no) and is a Microsoft Device Application Development MVP. Per Ola got his bachelor degree in Software Development back in 2005. Since 2005 he has been passionately working with mobility projects on a wide range of technologies and areas of use. Driven by his passion for this craft he spends a lot of his time off work to further explore technology possibilities or new programming languages or techniques. He finds himself privileged to be able to make a living from one of his hobbies. Per Ola has experience from a wide range of projects covering developing applications for the consumer market and for the enterprise market. He has had several different roles: developer, architect, team leader, project manager, technical resource in pre-sale and strategic planning. Per Ola is a DZone MVB and is not an employee of DZone and has posted 26 posts at DZone. You can read more from them at their website. View Full User Profile

Getting your WordPress plugin listed in the WordPress Plugin Directory

01.26.2011
| 4127 views |
  • submit to reddit

My DiveBook plugin is completed and I want it to be listed in the WordPress Plugin Directory. This way it will be easier for others to install and read about the plugin. Before you get your plugin listed there is a few steps you must do and a few steps I think you should do. In this post I will talk about what I did to make my DiveBook plugin ready for the world.

First your plugin needs to follow a few restrictions set by WordPress. Then you need to sign up, send request for WordPress to host your plugin and add your plugin to the Subversion repository (you get access to the svn repository when WordPress have read and accepted your hosting request). You also need to create a readme.txt file for your plugin. You can read about the steps above at the WordPress Developer Central.

When it comes to writing the readme.txt file you should spend some effort to make this file detailed and good. All the information a potential user of your plugin will read is parsed from this file. Most important is to have a good description about the plugin, screenshots of the functionality and a good description on how to install and use your plugin.

This is all you need to do. WordPress will automatically publish your plugin from the subversion repository.

Beside this I will strongly recommend you to make your plugin support I18N (Internationalization). This means that you code your plugin in a way that makes it possible to translate the text displayed to other languages. WordPress have good I18N support and you can read more about how to do it at I18N for WordPress Developers. If you want to start translating your plugin you should read this post: How to create a .po language translation.

You should also try to test your plugin on a few different WordPress installations running different themes. I was up for a surprise when I tested my plugin on another WP instance running a different theme. The UI looked like crap and I had to go through my stylesheet and make sure that I had added all styles that I needed to avoid these being overridden by other css files in the theme.

I started this post by saying that my DiveBook plugin is completed, that a white lie… The DiveBook plugin is now released in a Beta version and I will do some updates the following weeks and have a final release ready by the end of January 2011.

You can read about and install the DiveBook plugin at the WordPress Plugin Directory – DiveBook.

Some screenshots from the plugin:

Sidebar Widget

 

Main view

 

Log a dive

 

Update a logged dive

 

View details about a logged dive

References
Published at DZone with permission of Per Ola Sæther, author and DZone MVB. (source)

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)