Living in Divi

I build websites in Divi. There, I said it. Somewhere a developer who hand-writes every line of CSS just winced, and that is fine. I run a small digital marketing studio, my clients are small businesses with real budgets and real deadlines, and Divi is how one person ships a complete site in weeks instead of months.

For anyone outside the WordPress world: Divi is a visual page builder from Elegant Themes. You drag sections, rows, and modules onto a page, you style them with a settings panel, and what you see is what publishes. No staring at a blank template file. No pushing changes and refreshing to see if the padding worked. You are inside the page, shaping it.

That directness matters more than any feature list. When a client says the headline feels cramped, I fix it while we are on the phone. When they want a testimonial section, I drop one in, restyle it to the brand, and save it to the Divi Library so the next page gets it in one click. The feedback loop is minutes, not days.

Why a visual builder is the right home base

The honest answer is economics. A small business needs a good site for a few thousand dollars, not an agency retainer. At that price, the math only works if the tooling is fast. Divi's lifetime license was maybe the best money I have spent on this business: one purchase, every site, forever.

The second answer is handoff. My clients can edit their own sites. Not the layout, heaven help us, but the words, the photos, the hours on the contact page. A visual builder gives them a door into their own website, and that door is worth a lot of goodwill.

The third answer is the Theme Builder. Since Divi 4 I can design headers, footers, and templates for whole categories of pages, not just one page at a time. It moved Divi from a page tool to a site tool, and it is a big part of why I have not gone looking for another home.

The craft of hiding the builder

Here is the thing nobody tells you: a builder site does not have to look like a builder site. Most do. You can spot them from orbit: the stock layout pack barely reskinned, the default drop shadows, the same three-column icon row on every services page in America. That is not Divi's fault. That is a craft problem.

So the craft became my obsession. The builder gives you speed; taste has to come from somewhere else. Over a lot of builds I settled into rules that keep the tool invisible.

• Never start from a layout pack. Start from the brand, sketch the sections on paper, then build them up from an empty page.
• Set a real type scale and spacing system in Theme Options once, and stop making one-off font decisions inside modules.
• Kill the default animations. If everything slides in, nothing means anything.
• Use real photography of the actual business. Stock photos of handshakes are how a site tells visitors it does not care.
• Keep a child theme with a custom stylesheet for the last ten percent that Divi's settings cannot reach.

The child theme is the quiet hero in that list. Divi's options go far, but the difference between a builder site and a designed site usually lives in a hundred lines of custom CSS: tighter line heights, deliberate hover states, one accent color used with discipline.

The bill I know I am running up

Now the other column of the ledger, because I am not blind to it. Theme options sprawl is real. A color can live in Theme Options, in the Customizer, in a page's settings, in a module's settings, or in my child theme, and finding which one is winning is archaeology. Every site accumulates a little of this sediment.

The bigger worry is shortcode lock-in. Divi stores pages as shortcodes, and if you ever switch themes, your content comes out as a wall of et_pb_section tags where your beautiful pages used to be. I know this. I have made peace with it the way you make peace with a mortgage. But I think about it more than I used to.

And there is the tension inside WordPress itself. Core keeps betting on Gutenberg, the block editor, and now full site editing. Every release, the blocks get a little better, and the gap between what core does and what builders do gets a little smaller. Divi and Gutenberg mostly ignore each other on my installs, with the Classic Editor plugin standing guard, but two page paradigms in one CMS is one more than anybody needs.

Some designers I follow have decamped to Webflow entirely and will not stop talking about it. I am curious. I am also busy. For now, this is home: a visual builder, a child theme, a library of sections I trust, and clients who can afford the result. Speed is a feature. So is knowing exactly where the bodies are buried.