Creating and Using My Own Baseline Theme? Not Anymore

A few years ago, when my WordPress-based website firm was ramping up business I found myself recreating the same template files over and over. Starting with the same base and customizing as needed for the specific client need. After a short while, I discovered Foundation by Zurb, a mobile-first HTML framework that is easily modified to be a base WordPress theme to start a fresh website.

And I loved it. Since it was mobile first, any design I wrapped around the code-base looked great on any device, and the theme files were (or are) easy to understand and the framework itself is actively maintained and supported.

The problem as that it’s not a Child-Theme Framework, like Genesis is. If there was an update to Zurb Foundation (which there is about every few months), I would need to go back to every site used it on and make sure whatever they updated was compatible with my customized theme, and then update the files hoping I didn’t break the site.

Naturally this goes against the concept of having a Child Theme.

Then I discovered WP Beaver Builder, and it’s corresponding Beaver Theme and Child Theme. Since WordPress page builders are all the rage these days with WordPress developers, I researched a lot of them after learning about Beaver Builder and ultimately came back to it since it’s best-in-industry.

I purchased the Pro package, which comes with the Plugin and the Theme/Child Theme combo. Since this is a true WordPress optimized Child Theme Framework, I can safely use it on any number of websites. And when WP Beaver Builder updates either the plugin or the main theme, I can update everything with confidence that my site and my client sites will not break.