One of my clients use FoundationPress as their starter WordPress theme, so as a test of my adaptation skills I decided to test it out by building a bespoke WordPress theme based on the designs they provided. Despite the theme being deprecated, meaning there’s no active developer/s maintaining it, it’s simplicity allows it to run flawlessly as of 29/02/2020.
In summary, FoundationPress is a WordPress starter theme that integrates the foundation front-end framework. It has a really organised and intuitive structure, utilising gulp and sass. One thing I really love is the ‘library’ directory which stores all the stray pieces of PHP that’s usually thrown into the functions.php file in individual files. To summarise I’ve highlighted, in my opinion, three reasons to use and three reasons to avoid using this starter theme for your next bespoke WordPress theme build.
Amongst all the starter themes I’ve used, FoundationPress is by far the most simple to use. From using gulp to easily manage your assets and production builds to having intuitive directory names to manage all your PHP. Moreover, FoundationPress includes a starter SCSS directory with a ‘_settings.scss’ file. In this file you can easily configure your grid, enabling you to change the breakpoints, gutter size and even the number of columns, based on the foundation framework.
Although these are fairly easy to set up, FoundationPress configures gulp with all the functions you could possibly need to instantly build your production assets for quick deployment to your live server. By running npm run build, this runs the gulp production methods, reproducing your dist folder to contain your minified CSS and JS ready to deploy.
Although the starter theme still works with no hiccups as of 29/02/2020 the lack of anyone supporting it going forward could lead to compatibility issues. As you’re probably aware software improves and accelerates consistently and without testing, that’s when things start to break.
The primary reason you would use this starter theme is for the Foundation framework. If it’s your go to framework for most of your builds then ignore this point but if you prefer say Bootstrap, then I’d recommend using an alternate starter theme to avoid the headache of removing the already baked in foundation framework code. On the other hand, as mentioned earlier I would definitely still mimic the overall structure of the theme, maybe fork the GitHub repo and remove the foundation related parts, just an idea.
You’ll notice on the GitHub repo you can run the command
npm run package, which packages all your themes folders and files, including your minified assets, into a zip folder ready to upload as a theme. However, I needed to include a separate ‘icons’ folder in the root of the theme that contains global icons like the logo and unfortunately, this command ignores any other folder and files it is not instructed to include. More of a minor luxury but would save time.
If foundation is your front-end framework of choice, then I couldn’t recommend it more. Its simple and intuitive structure allows for a comfortable build and the ability to use modern tools. However, if you’re not interested in foundation and prefer it’s mighvty cousin Bootstrap, for instance, then maybe consider another starter theme or better still, replicate the theme structure and remove the foundation parts as mentioned earlier.