Building your own Boilerplate

Recently, I gave a talk about workflows at the Utah WP meetup and one point I mentioned was to create your own boilerplates, for a plugin or a theme.

Naturally, I assume you already try to use a boilerplate a lot of the time, but it may be one you use from another source and you only make modifications after you download it. But I believe that dedicating time to building your own boilerplate or taking an existing one and heavily modifying it to be reused throughout many projects is well worth. I didn’t think it was at first, but the time you can save by writing one dedicated to your business work can really be beneficial for you and your potential employees.

For theme developers, taking the _S theme and tailoring it to a cookie-cutter layout and with your dependencies to improve your workflow with clients who need a theme or if you plan to have a line of themes with similar javascript and a similar functions.php.

For plugin developers, If you build a lot of extensions for a plugin, build a boilerplate and release if the parent plugin doesn’t have one yet. Other than that, again , build a boilerplate that will make it super easy for you to generate plugins faster and more efficiently.

Like I said, try building your own or go with one that exists. I personally like to build my own with inspiration from existing boilerplates, but not quite a copy and paste.  In this day and age, a solid workflow is quite important and it’s good to keep working faster and smarter.   

Published by

Nikhil Vimal

Hi, I'm Nikhil, a WordPress developer and open source nut. I am the Founder and Developer at

Leave a Reply

Your email address will not be published. Required fields are marked *