Opens in a new tab
Building, Testing, Writing

WordPress and Bricks

I've been using WordPress since 2008 and Bricks Builder since 2021
Last Modified: 28 September 2026

WordPress has been my platform of choice for years, and nothing has come along to shift it. Bricks Builder, and Oxygen before it, lets me drag a layout together when that is quicker and drop into code when it isn’t. Then there is the plugin library, which means most of what a client asks for has already been half-built by somebody else.

The WordPress editor, on the other hand, is tedious in the extreme. So every site I build pairs Bricks with ACF Pro, and every word, image and link on the page lives in a field the client can find and change without calling me.

Bricks Builder and Advanced Custom Fields make WordPress hard to beat.

The tools

Simple, original layouts, built quickly, with code on hand for the bits drag and drop cannot reach.
Folders for pages, templates and media, and the folders do real work: Bricks reads them to decide which header and footer a page gets.
The door Claude uses to get into the site. Fields, classes, templates and whole sections go in through it, straight into the database. There is no other way in.

Notes

The catch with WordPress is that everybody uses it, hackers included. It needs constant updating, and I don’t just mean WordPress and its plugins. Everything about a site needs looking after. Build one, walk away, and it goes stale.

Maintenance, the way I do it, means watching how a site performs and tweaking it so it keeps getting better, whether that means more visitors or more of them getting in touch.

From the notebook