Software Engineering in WordPress, PHP, and Backend Development
Information, updates, and other posts related to my WordPress Widget Boilerplate that serves to provide a solid foundation for building WordPress widgets.
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.
In the same way that I’ve been working on the WordPress Plugin Boilerplate, I’ve never really done a good job of handling versioning. I’ve simply closed tickets as they’ve been opened and I’ve resolved issues as I – or others – have encountered them.
Next month, I’m hoping to officially tag it and the WordPress Plugin 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 both of the boilerplates to improve its overall standard.
Here’s a run down of everything that’s been updated since the I initially launched the WordPress Widget Boilerplate:
Over the last few months, the WordPress Widget Boilerplate has received a number of pull requests, merges, and improvements.
A few months ago, I contributed an article to WPTuts on Writing Maintainable WordPress Widgets. The motivation for this series was driven largely by the fact that as much as I love the WordPress community, there are more than a few poorly constructed plugins.
In some cases, this is fine. If you’re planning to quickly throw something together with no plans to continue development after its initial release, you can probably get a way with throwing something functional together.
But if you’re looking to build a plugin that you’ll be maintaining over time, then I believe applying good software development practices is a must. That is, I think that developers should follow the platform’s API, use design patterns where applicable, and clearly organize their files.
© 2024 Tom McFarlin
Theme by Anders Noren — Up ↑
