A few years ago, I started the WordPress Plugin Boilerplate project as nothing more than a GitHub repository used to store code that I found myself frequently using in both personal and client projects.
As I became more involved with WordPress, as I began to build more plugins for fun and profit, and as I began updating the repository, it grew into something a little more than I had expected.
Over time, people began to open issues, offer pull requests, perform code reviews, and create their own forks of the project. I learned a lot over the next few years, and I honestly couldn’t be more excited to see such a little project become, you know, such a slightly less little project.
Months ago, I mentioned that work on the next iteration of the WordPress Plugin Boilerplate was started and I’m excited to announce that, as of today, the WordPress Plugin Boilerplate 3.0.0 is officially ready for use.
And it comes with a lot of new and neat things to boot.
In 2011, I released the first version of the WordPress Plugin Boilerplate and have been maintaining it (along with contributions from other programmers) ever since.
Over the last couple of years, the Boilerplate became quite active – as far as very small projects are concerned – with issues, pull requests, and so on. It’s been a lot of fun to maintain, and it’s been really neat to receive so much feedback from other developers in terms of making the Boilerplate more resilient and from those who were just getting started with plugin development.
Earlier this year, I shared that I – along with a small group of other people – began working on the next iteration of the WordPress Plugin Boilerplate. That is, we were initiating a complete rewrite of the project.
As of today, I’m officially launching a beta of sorts of 3.0.0 of the Boilerplate. This is a major rewrite and refactoring of the Boilerplate in the state that its had for the past few years, and there’s a lot of change coming not only to the Boilerplate itself, but to new site, documentation, forks, and so on.
One of the things that I’m working hard to have released by the end of the month is the latest version of the WordPress Plugin Boilerplate.
The latest version has been in development for quite a while now (a lot has happened offline so, you know, that’s how it goes).
The last time that I really spent any time talking about this project was in November 2013. A lot has changed since then. Initially, I was planning on a minor upgrade with some of the following features:
- Releasing the version has part of the 2.x.x versioning
- Including a class specifically for administrative functionality
- Fixing issues with symbolic links and textdomains
- Including more TODO’s for users to find what needs to be changed
- …and so on.
But when I got started on the next version of the Boilerplate, a lot of things changed. The short of it is that it’s being completely re-written from the ground up and the code and documentation are being split into to separate things for the sake of user education.
I’ll spend more time talking about the Boilerplate in a future, but one of the things that I wanted to share that’s related to running a project like the Boilerplate has to do with open source, contributions, lack of a vision, and how this can negatively impact your project and your users.
As discussed earlier last month, the next version of the WordPress Plugin Boilerplate is currently in development.
For those who are interested:
- You can find the current stable version on GitHub.
- The `develop` branch to which the core team and I are working (though we’re not currently accepting pull requests).
- And you can read about the changes in the upcoming version in this previous post.
The foundation of the status of the next version of the Boilerplate currently leaves a lot to be desired, but the team and I – along with the help of Slack (probably a topic for another post ) – are in the process of planning the upcoming website that will accompany the project.
The problem? We’re all developers, but we need a logo.
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.