So, over the years of building WordPress sites across Kansas, I’ve had one recurring challenge — balancing powerful design freedom with a simple editing experience for my clients. Most of them just want to log in, make a quick change, and get back to running their business — without worrying about “breaking” anything. And honestly, that’s how it should be.
That’s why I started blending the native WordPress Gutenberg editor with advanced page builders like Bricks Builder and Oxygen. It gives me total creative control while letting my clients enjoy an easy, familiar interface. About 80% of their content is edited right inside WordPress — the part they already know — and the other 20% (the complex design and functionality) lives inside the builder. It’s a workflow that just makes sense — clean, scalable, and built for real-world use.
When I first started using page builders, I used to put everything inside them — text, images, layout, you name it. But over time, I realized that gave clients way too much to manage. They’d log in, open a complex interface, and either (1) break the design by mistake, or (2) never touch it again out of fear. Both of those are bad outcomes for long-term growth.
WordPress became popular because it’s user-friendly. So I decided to keep that spirit alive — now, clients can edit content in Gutenberg (the native WordPress editor) while I handle the more complex visual work inside Bricks or Oxygen. It’s the best of both worlds — clients can stay confident, and I can make sure the design never breaks.
In simple terms, I design custom templates inside Bricks or Oxygen. Each template includes a special “Post Content” area that dynamically pulls in whatever content is written inside the WordPress editor. So, when my clients log in to write a new blog post or update a service page, they’re doing it the same way they always have — through Gutenberg. The layout, colors, and design never change because that’s locked into the builder templates.
In Bricks Builder, I drop in the Post Content element where the editable area should be. Then I wrap it with the custom layout, featured images, headers, and dynamic components. Clients just write their posts as usual, and Bricks automatically displays them beautifully.
In Oxygen, I sometimes use the Gutenberg Client Mode, which hides the builder entirely from clients. They just see their pages as editable Gutenberg blocks — text, images, backgrounds — without even knowing Oxygen is running under the hood. It’s a slick system that keeps things foolproof.
💡 Small tip: the more I keep clients inside the default WordPress experience, the fewer support emails I get. That’s not a coincidence — it’s by design.
I follow what I call the “80/20 rule” — roughly 80% of a site’s content is managed directly in WordPress, and 20% stays in the builder. That 80% covers all the easy-to-change stuff: blog posts, service descriptions, team bios, testimonials, and announcements. The 20% includes things that shouldn’t be touched often — like headers, CTAs, pricing tables, and more advanced layout structures.
This separation keeps things scalable. Clients get freedom where they need it, and I keep control over the parts that protect performance and consistency. It’s also faster for me to update templates later without touching content, which is great for ongoing site maintenance.
Every client who’s switched to this hybrid setup tells me the same thing — “This is so much easier.” They can publish a blog, edit a paragraph, or swap an image without opening a complicated builder panel. Meanwhile, I can create more beautiful, stable sites without worrying they’ll get messed up later. Win-win.
For advanced projects, I also integrate ACF Pro (Advanced Custom Fields) to give clients even more control. For example, if they need to update a testimonial or staff section, they can do it through structured fields — no coding or design adjustments needed. I also use GutenBricks to convert certain Bricks layouts into reusable Gutenberg blocks. It’s a flexible way to give clients branded, drag-and-drop content components.
Over time, this approach builds a library of reusable, consistent blocks across all of my Kansas web design projects. It saves hours and keeps every site on-brand without starting from scratch.
At the end of the day, web design isn’t just about fancy visuals — it’s about creating something that clients can actually use. I’ve learned that empowering clients with confidence pays off more than building flashy sites that require constant hand-holding. The Gutenberg + Bricks/Oxygen combo is how I make that happen.
If you’re a web designer looking for a way to scale your projects or a Kansas business owner wanting a site that’s both beautiful and easy to manage, let’s talk. You can check out how I’ve implemented this across real client projects on my portfolio page or reach out directly through my contact page. I’d love to show you how seamless a WordPress site can really be.
