WordPress Plugin Boilerplate

Information, updates, and other posts related to my WordPress Plugin Boilerplate that serves to provide a solid foundation for building WordPress plugins.

How We’re Planning The Next Iteration of the WordPress Plugin Boilerplate

Months ago, I announced that there was going to be a major update to the WordPress Plugin Boilerplate.

Because of its nature in being a hobby project, because this project is something that’s being worked on by a number of contributors, and because the next iteration is going to be a major rewrite of what we have so far, it’s taking a while to begin pushing code for the new Boilerplate.

But there are a lot of neat things coming, and I think that even if it’s taking us a while to get something on GitHub, it’s worth providing updates as to where we currently stand with the project.

The Latest Branch of the WordPress Plugin Boilerplate

Just shy of a month ago, I shared some information about the state of the WordPress Plugin Boilerplate.

Specifically, I mentioned the following:

  • We’re working on rewriting it to be cleaner, easier to understand, and more flexible for developers of all experience.
  • I’ve got a small, core team of volunteers helping me out (who I greatly appreciate).
  • Where we’re headed with this latest version of the project.

To be honest, I’ve never been more excited about the project.

There’s a lot more coming down the pipeline that I’ll cover later in this post – I also want to clear up some fun versioning quirks that I’ve been asked about – but I wanted to give a heads up on the current state of the codebase and where you can follow along with the development as we begin to push code.

The State of the WordPress Plugin Boilerplate

One of the projects that I love working on the most is the WordPress Plugin Boilerplate.

I dig it because it’s been a resource that has helped other people, and there are a number of other contributors that are constantly working to make it even better.

Earlier this year, I had plans to begin releasing more frequent updates, but – as with the nature of employment and side projects that are done for free – the updates didn’t happen as fast as I would like.

Additionally, it was becoming clear to me that the Boilerplate was headed in a direction that was going to be more intimidating for beginners, harder to grasp for those migrating their plugins to that format, and that it was not using some of the best principles in place.

So after talking with a number of notable developers, I’ve opted to delay the release of 2.7.0 until we have something significantly better than what’s in place.

In fact, it’s going to be a near total rewrite.

The WordPress Plugin Boilerplate 2.6.1 is Now Available

For those who are interested in following future development, sign up for the mailing list!

The next version of the WordPress Plugin Boilerplate is officially tagged and available for download in GitHub.

This release – although a minor improvement over the last – introduces several improvements to 2.6.0, and also marks a change in the development of the project, as well as the introduction of several things that will be coming to the Boilerplate in the next several versions.

Subscribe For Updates: The WordPress Plugin Boilerplate

With yesterday’s announcement of the latest release of the WordPress Plugin Boilerplate, I’ve had a number of emails, tweets, and messages how people can stay up to date with the project without having to follow the GitHub repository, or the blog.

Ultimately, I want to make sure that this Boilerplate reaches the largest number of developers both for those who wish to contribute, and for those who wish to use it as a starting place for their projects.

As such, I’ve created an opt-in mailing list to which you can subscribe.

The WordPress Plugin Boilerplate 2.6.0 is Now Available

For those who are interested in following future development, sign up for the mailing list!

Today, I am absolutely stoked to announce the next major release of the WordPress Plugin Boilerplate.

I discussed some of the things I’ve learned – and some of the changes that have been implemented in a recent post – but I couldn’t be happier with this release.

Some quick statistics:

  • The last official release was on May 17, 2013. We had one minor release in July that I opted to fold into this release and officially tag as 2.6.0.
  • We’re now working to implement semantic versioning into the Boilerplate.
  • The milestone for 2.7.0 is already being planned.
  • The project now includes 241 commits and 10 contributors

This is by far the largest commit and set of changes that have gone into the Boilerplate since it has been released. You can grab it here, but read on for more details!

Preparing For The WordPress Plugin Boilerplate 2.6.0

The WordPress Plugin Boilerplate has been a bit of a pet project of mine a little over the past two years.

In that time, it’s grown from something that I was using to jumpstart my own plugin development efforts into a more mature boilerplate that provides a significant number of features specifically to help developers get started with best practices in developing WordPress plugins.

However, that maturity has happened not because I’m the one who has been constantly contributing to the project, but because it has received so many awesome pull requests and discussions from others.

And with my getting ready to release 2.6.0 of the Boilerplate, I’m looking for one final push!

Announcing The WordPress Plugin Boilerplate 2.0

Back in December 2011, I released an initial version of the WordPress Plugin Boilerplate. The purpose of the boilerplate was to provide an easy way to build WordPress plugins.

Specifically, the project featured:

  • File organization
  • Documented code
  • Implementation of the Plugin API
  • Action and Filter Reference

After the feedback that I received upon thisl release, I officially published version 1.0 to GitHub on November 29, 2012. After over a year of various contributions from others and other improvements, I’m proud to release the second version of the WordPress Plugin Boilerplate.

WordPress Boilerplates: Widget and Plugin Officially at 1.0

Earlier this month, I mentioned that I was looking to bring the WordPress Widget Boilerplate and the WordPress Plugin Boilerplate to 1.0. Throughout the month, I received a several pull requests most of which I merged into the projects.

I made a few changes that I’ll detail momentarily, but as of right now both WordPress Plugin Boilerplates are officially tagged as 1.0 and are available in their respective GitHub repositories.

WordPress Plugin Boilerplate: Aiming For 1.0

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: