When beginning writing plugins for WordPress, most developers will publish the fruits of their work in the official WordPress.org Plugin repository. It’s a great way to get into plugin development for your favorite CMS. I started this myself in June 2011 and so far it has gotten me lots of experience on how to code better and manage the whole process. My Experience If you’ve already published on WordPress.org or plan to do so, your plugin or theme is required to provide a so-called “readme.txt” text file. This is required because the repository parses it with Markdown language and draws all appropiate information from it, which is then displayed on the public repository. The header of that file also controls all aspects of the title, tagging, author, donate link etc. for your plugin or theme. So, in this tutorial I’ll give you a lot of tips on how to do it the right way, based on my experiences over the last six months. I’ve seen so many great plugins in the repository but only a few have great descriptions and documentation. A lot of plugins have very minimal descriptions and documentation and leave the user alone. We want to change this. All readme files are split into sections and
Share This