Only header ( === Plugin name === ) and short description ( in that order ) must be on top. Other sections ( == section == ) can be placed in any order. Your == Changelog == can go just below short description, not higher.
You can ship translations of some of the metadata used in your main plugin file’s header comment fields. Namely: Name, Description, PluginURI, Author, and AuthorURI. Just add the source strings into your PO/POT files exactly as they appear in your plugin headers. When a MO file is available containing these strings, WordPress will display the … Read more
It would be better to include your own CSS file that way you can: Use a relative path to your CSS. Avoid problems getting the path right to the wp-admin directory. Not all people put WordPress in the root directory, so your example above would break for them. Possibly redundancy by reusing the CSS in … Read more
There’s a bug in the parser with regards to short descriptions. I’ve just been fixing them manually for now when I run across them. Regardless of the reason for the error, you get much better results if you ask the plugins team directly instead of posting somewhere else. We have an email address. plugins @ … Read more
The code used on wordpress.org to render readme files is here: class Markdown. You can download the class and the dependencies, then you should be able to set up a simple custom reader. If you want to see it as close as possible to the actual page, you can download/checkout per SVN the theme from … Read more
While I cannot remember on top of my head live example of plugin with a gif, there are quite a few with videos and at least ones using animated PNG as header (AJAX Comment Loading). So I would say — yes you can, but no guarantee it will end up well. It’s not explicitly forbidden … Read more
When you look at the plugin description (and other sections), it all comes from the current version README.TXT file. So if you upload a changed version of README.TXT to the current version’s repository (not changing the repository version number), the newly updated README.TXT file information is shown on the page. This is great for updating … Read more
Very simple, All you need to create a image of size exactly 772×250 pixel and name it as banner-772×250.jpg. You have to save this image in /assets/ folder in your plugins SVN directory. Make sure the image is of either .png or .jpg type. The .gif images are not allowed. It may take upto 15 … Read more
Yes. You need to: Change stable tag to 0.2 Commit (or copy/branch) new version to /tags/0.2 Don’t forget to update version to 0.2 in plugin’s header
Try this markdown: I think you can link directly to the raw version of an image if it’s stored in your repository. i.e.