For a long time, I’ve always started projects in the same way.
My foundation consists of the following:
And more recently, I’ve well and truly ‘latched-on’ to Beaver Builder.
But then, as many developers do, have a framework of code utilities that allow me to avoid repeating code for future projects. My framework is called Fuelled. Fuelled is, shall we say, not fit for public consumption, hence no link. It’s always being refactored, and there’s barely a comment in sight.
Fuelled is also pretty large. Over time, lots of stuff has been added, and very little taken out.
There are swathes of helper functions to help me pick apart data collections, reroute mail for development sites, and debug stuff. And these are cool; I like them a lot. They can stick around.
But it also:
- Registers a theme options UI, so I can set stuff like a logo, contact details, social profiles and more
- Allows me/users to register navigation menus and widget areas
- Hide/display a promo bar that sits at the top of the screen
- Add font packs from Google or Typekit
- Add icon packs from Icomoon
- Set API keys for things like Google Maps
- Configure the header and footer, such as choosing nav menus, logos for different contexts and choose whether to make sticky or not
On top of that, I had a very modular and complementary SCSS project, which worked with Fuelled. It spanned approximately 80 files and contained thousands of lines of CSS, and would serve as the base for any new project.
And it’s worked really well. It almost saved me some time, once, but as I insist on refactoring it with every new project, I think I’m only break-even.
But then, Beaver Themer came along. If you’re not familiar with this piece of awesomeness, then get familiar – sharpish. It allows you to build your entire site, including areas outside of the content area such as headers, footers and archive pages.
With that said, I hadn’t really intended to use it just yet. I’ve always found headers and footers to be fiddly, and to avoid looking ‘templatey’ would need to be hand-built each time. Every client seems to want something unique in there.
But I couldn’t resist.
I’ve been working on a client project for a few weeks now, and snuck Themer in. And to cut a long story short, I’ve commented out nearly 50% of my beloved Fuelled framework, and I’ve only included about 500 lines of SCSS for a custom WooCommerce checkout.
So why am I boring you with all of this?
I’ve added a new thing to WPD BB Additions!
Although not specifically for Themer (it will work on any row), it will likely work best with it. It’s the ability to create a collapsible row, and optionally set a cookie.
Here’s one in action:
You can set:
- Close icon + size + colour + position
- Close speed
- A cookie, so once this is closed, it stays closed for a certain number of days
Expect to see it as an update in the next couple of days!