BoilWP’s boilerplate generator is beta ready. Come check it out. http://boilwp.com
I tried it but (like the other plugin boilerplate that’s out there) it’s too object-oriented for my personal taste. My own plugins are more straight-to-the-point and have a lot less code/classes/functions than what this boilerplate has, so I’m (easily) thrown off by the stuff in there that I’m not sure what to do with. I mean, the results of a randomly generated boilerplate (without actual functionality) already has tons of code, more than my own plugins that have full functionality.
I’ve said it before on here, but I honestly don’t know if this object-oriented method is significantly better than my “traditional” way. So personally, I’d say “it’s not for me” but I can’t speak for others who DO use the object-oriented way of programming. Although it looks like it could be super helpful!
Out of curiosity, what does the “#1” part refer to?
The purpose of the generator is to simply replace strings, variables, function names, class names and so on. Then you can start to develop the functions of your plugin.
There are two plugin sizes. The “Standard” size is for those who are building a plugin that will be updated and improved over time with the community such as
The “Small” size is for plugins that are not going to be updated so much and need very little.
At the moment, I don’t have any documentation for any of my boilerplates and the code library is empty because I am very busy.
BoilWP, as it is now is the first step I have taken to provide the resources and tools for developers to build their plugins and while it is still very early, over time more and more will be provided. BoilWP has been done purely out of my own time that I have spare and 2 other volunteers who have helped me pushed the project further.
I prefer to use the object-oriented method because when I started to develop plugins I was still learning PHP and WordPress. Since then I have improved my ability to code and to code well.
With that, I also found myself writing the base of the plugin each time I wanted to develop a plugin or when I was hired to develop a plugin. This started to slow down my progression time and after a while I got tired of it so I decided to write the best structure that would allow me to just tweak a few things here and there before I start to develop the plugin.
After a while, I also ended up developing two more boilerplates specifically for WooCommerce.
I put #1 to refer as the only place a WordPress developer would need to go to generate a plugin.
I guess it’s just a different methodology, basically. Perhaps I should make my own boilerplate for non-object-oriented plugins.
I’m not sure if it’s the only place, really. See: http://wppb.io/
Thanks for sharing this here. First of all, I think it’s really cool that you’ve open sourced all the BoilWP stuff on GitHub.
The boilerplate that is linked on http://wppb.io/ is Tom McFarlin’s WordPress Plugin Boilerplate which has passed ownership to Devin Vinson. BoilWP is my own version and is more jet-packed if you like.
Looking for more Volunteers. https://trello.com/c/wt3lYVdI/16-looking-for-more-volunteers-interested
Nice work @seb86 - I love seeing these boilerplates and templates popping up
@Senff This is not for any self-promotion, but my plugin template might be more helpful for you: https://github.com/hlashbrooke/wordpress-plugin-template - it’s object-orientated, but not to the extent that @seb86’s or Tom McFarlin’s boilerplates are (for better or worse), so the classes are fairly easy to understand and navigate. I actually just created it for my own use, but it’s proved to be relatively helpful to some other people too, feel free to use it if it works for you.