The purpose of the course was to provide the initial set of documentation for the project that would give users and developers a complete walkthrough of the source code, understanding its organization, and a tutorial for how to build a plugin with the project.
Over the last few weeks, I’ve talked about some of the changes that I’ve been looking to make over the coming weeks primarily so that I can re-focus my efforts. Specifically, I talked about this in this post and in this post.
When I first launched the landing page for the WordPress Plugin Boilerplate last year, the main idea was to grow a site around the single landing page that offered code examples, how to’s, and other forms of documentation.
But I’ve spent the last month working on some special material for the Boilerplate (that I’ll talk about in an upcoming post) which got me thinking more about what I wanted to offer in terms of documentation for the project.
Since the release of the latest version of the WordPress Plugin Boilerplate, the top two things that people have requested are documentation complete with examples, and a generator to ease the pain of having to replace certain tokens throughout the boilerplate’s codebase.
And I’m all for it – I’ve even committed to begin providing this material in early 2015 (and not just via the project’s website, but a few other channels, as well – more on that later). The awesome thing about open source is the contributions that can come from other people.
Sometimes these come in the form of patches or pull requests, other times they come in the form of extensions, enhancements, and other types of projects that help improve the initial project.
A little over a month ago, I released the latest version of the WordPress Plugin Boilerplate. The response has been great – more than I was expecting, really but that’s a good thing – and, generally speaking, it’s been overall positive.
Over the last month or so, it’s become clear that more time and resources will be needed to focus on the Boilerplate and to continue to refine its codebase, its functionality, its documentation, and so on. The bottom line is that I want to make sure that I get the right – or as close to right – as possible during the first try.
To that end, I need some input from others (read: you).