WordPress Plugin Boilerplate

Since I’ve been working on the WordPress Plugin Boilerplate, I’ve never really done a good job of handling versioning for it. Instead, I’ve closed tickets as they’ve shown up and I’ve resolved issues as I – or others – have encountered them.

Next month, I’m hoping to officially tag it and the WordPress Widget Boilerplate as version 1.0, but I’m hoping to get a few more eyes on the code prior to doing so.

This weekend, I spent some time closing tickets, refactoring some code, and improving a few aspects of the code to improve its overall standard.

Here’s a run down of everything that’s been updated since the I initially launched the boilerplate:

Updates To The WordPress Plugin Boilerplate

  • Removed an unneeded closing brace
  • Cleaned up the code to comply with the WordPress Coding Standard
  • Added default README requirements
  • Resolved issues with JavaScript and Stylesheet paths being incorrectly imported
  • Changed from plugins_dir_path to plugin_dir_path
  • Added activation and deactivation hooks in the constructor
  • Resolved typos in plugin-specific JavaScript and stylesheet issues
  • Removed the closing PHP tag
  • Removed ampersands on $this for changes in pass-by-reference changes in PHP 5.4.4
  • Updated JavaScript to conform to JSLint standards

Of course, many of these couldn’t have been done without pull requests and contributions for others on GitHub. I’m certainly not taking credit for all of the work that’s been done!

What’s Needed For 1.0?

Generally speaking, I think that the WordPress Plugin Boilerplate is almost ready for 1.0, but I’d like to have as many of you code review it as possible.

Ultimately, I’d love to have this become the de-facto boilerplate for creating WordPress plugins so if you have five minutes and feel like opening a ticket, contributing a pull request, contributing some other change (even if it’s a feature request), please do.