
Now that your plugin has been approved for hosting in the WordPress Plugin Directory, you’ll need to learn a bit about how the Plugin Directory works. The Plugin Directory works with a certain structure of Subversion repository, and you will have to adhere to this structure to have your listing work correctly.
When your Subversion repository is setup for you, you’ll have three directories in it – trunk, tags and branches. These directories help separate the development of your plugin from your stable versions. Development of the very latest version is done in trunk. When that development is stable and ready for release, you copy the files into a subdirectory in tags. Files in tags should not be changed after they have been released to the public. branches can be used for the development of lesser versions than that of trunk. For example, you may be actively working on version 1.2 in trunk but you could have a subdirectory for the development of version 1.1 in branches (for fixing bugs or security issues).
To add information to your plugin listing, you must create a file called readme.txt in your repository. This file will contain information such as the name of the plugin, the description and anything else you see fit. The plugin directory will automatically create a zip for download of your plugin files. It will initially look in the trunk directory for these files, unless it is instructed to look in a specific tag in the readme.txt in trunk. If you’re following the above structure, you would have a readme.txt in the trunk and one in each of your tags subdirectory.
In the trunk version, you would have the Stable tag: set to the version of the current stable version in tags (those subdirectories should be named as the version) and the rest of the file would be ignored (so you can develop your plugin listing along side your plugin). The readme.txt in the referenced tags subdirectory would then be used for your plugin listing. The plugin files in this subdirectory would then be used for the zip available for download on your listing page.
You can see an example/explanation of the readme.txt file here. In our next article we’ll be covering how to check in (or commit) your plugin into the Subversion repository.




