Tips & Tutorial

Tips for Developing WordPress Plugins

Oleh takien
WordPress
WordPress

Do you love WordPress? Having may sites built with WordPress. Got many advantage from free plugins out there? It’s the time to give back to the community. Making WordPress plugin. Especially free plugins. This is not a tutorial, just a tips if you want to make a plugin. Here is my tips for new plugin developer. Note that it’s my old draft — I don’t know why I wrote this last day —  so, may be there is an irrelevance to be applied right now. And note that, I’m not doing all of these, but it’s worth to try.

1. Before everything

  • Before you decide to make a plugin and publish it as opensource (to WordPress org), it’s recommeded that you make some research to know if your plugin will be useful to others (and make sure there’s no identical plugin out there)
  • If it not possible (likely it is), make sure you serve better plugin or with different approach.

2. Make your plugin attractive

  • Naming; plugin name must be easy to remember, representative, and simple. Generic if possible. Avoid embed your name (or your website,company etc) in your plugin name. Do not use trademark name.
  • Cover image, plugin with cover image is more attractive to the user. Prepare image named banner-772×250.png, place it on /assets directory (/assets directory is in the same level with /trunk directory)
  • Screenshots, don’t forget to include screenshots in your plugin (place it under /assets directory, named screenshot-1.png and so on), give description for each screenshot.
  • Now you can also provide plugin thumbnail to be shown in plugin search page on WordPress admin.

3. Support and accept feedback

  • Always check for your plugin support forum on WordPress org. Answer the questions from the user. For this, I can only check it for at least once per month.
  • Some users usually post some feedbacks/critics to your plugin. Do not be offended if they give negative feedback. Note each feedback for your future plugin development (update).

4. Keep update

  • What to update? the first thing you must update is users request. As in point #2 above, you should note all feedback and make it as new feature/fix in the next update.
  • Write down your todo list about your plugin. But don’t force yourself to make it.

5. Assets

  • You do not need to create all assets your own, such as CSS, JavaScript, icon, image etc. There’re many resource over the Internet. Make sure they’re licnesed under GPL, Creative Common or opensource.
  • If you’re unsure, ask the creator if their stuff can be used in your plugin.
  • Give credit to the author, if you use those assets don’t forget to give feedback link to the original author.

6. Coding

  • Use WordPress coding standard to code your plugin
  • Give comment to your code. It will help you in the next development and others.
  • Avoid use WordPress or PHP deprecated functions.
  • Pay attention with security issues.
  • Do not encode your code, otherwise it will be rejected by WordPress plugin reviewer.
  • Make sure you test your plugin in some WordPress instalation (current version and previous version), also test on live site (not only on localhost), if possible also test on diffrent server environment (eg. Linux and Windows)

7. Don’t

  • Do not force users to donate you. I saw some plugin author placed BIG DONATE BUTTON on plugin setting page and keep alert us to donate. This is kind of annoying. They will donate if they want to.

8. Promote your plugin

  • Do not spam to promote your plugin
  • Use social (Twitter, Facebook etc) to share your plugin
  • Post a video tutorial about your plugin in Youtube will boost your plugin popularity
  • Post your plugin in your blog/website
  • Use your own plugin in your client project if needed (If you’re web developer)

9. Use it

  • You should also use your own plugin for your own wesite. Act as you use other’s plugin. By doing this you will know what your plugin bugs, error, advantages, disadvantages, etc.

10. Keep update with WordPress Development

  • It’s important. You need to know what happened to WordPress community and code right now, and the future. Subscribe to it’s developer newsletter is a good choice.
  • And here is a place the you should frequently visit, https://make.wordpress.org/plugins/

Tulisan ini sudah berumur: 11 tahun 9 bulan 20 hari. Informasi di dalamnya mungkin sudah tidak relevan, tapi nilai historisnya sangat berharga, terutama bagi saya sebagai penulisnya.

Tag Terkait: