The Page Builder Builder

Most WordPress page builders give your clients the same interface you use to design.

That sounds democratic. In practice, it creates problems.

When clients have access to unlimited layout options, spacing controls, and typography settings, two things happen:

  1. They break things accidentally
  2. You spend time fixing what they broke

The alternative isn't removing their access. It's designing what they see in the first place.

The Client Access Problem

Here's a pattern agencies know well:

You build a site in Elementor or Divi. The design looks great. You hand it off to the client with access to the builder so they can update content.

Three weeks later: "The homepage looks weird. Can you fix it?"

What happened? They tried to add a section. Dragged something into the wrong container. Changed a margin value. Deleted a column accidentally.

They weren't being careless. They were using a tool designed for designers, not content editors.

The problem isn't the client. It's giving them a tool with hundreds of options when they need three.

The Traditional Solution

Experienced developers solve this with Advanced Custom Fields and Flexible Content.

Instead of giving clients a page builder, you create custom fields for specific content types. Clients fill in forms. The theme renders the design.

It works. But it's time-consuming to build.

For each component (hero section, testimonial block, image gallery), you need to:

  1. Define the ACF fields (text, images, options)
  2. Write the PHP template that renders the component
  3. Style it with CSS
  4. Make it responsive
  5. Test it thoroughly

A typical agency site might have 15-20 components. That's days of development before you can show the client anything.

What TheDock Does Differently

TheDock lets you design these components visually, then exports them as ACF Flexible Content fields.

You build the component once in a visual interface. TheDock generates:

  • The ACF field definitions
  • The PHP template code
  • The CSS styling
  • Responsive behavior

The client sees a curated library of components they can use. They can't break the design because they're not designing—they're filling in content fields.

This isn't a new concept. Agencies have been building this manually for years. TheDock just makes it visual instead of code-first.

Developer Experience vs. Client Experience

Traditional page builders optimize for one interface that tries to serve both audiences.

Elementor gives you hundreds of widgets and infinite customization. Great for building the first version. Risky when you hand those same controls to a client who just wants to change the headline.

TheDock separates the experiences:

Developer view: Visual builder with full design control. You create the components and define what's editable.

Client view: Native WordPress interface. They see only the components you designed. Each component has specific fields—headline, text, image—with no layout options to break.

When you export, the site runs on ACF and native WordPress. Disable TheDock and everything keeps working.

When This Matters

This approach makes sense if:

  • You build multiple client sites regularly
  • Clients need to add content after launch
  • You want to avoid support calls about broken layouts
  • You value workflow efficiency over unlimited flexibility

It probably doesn't matter if:

  • You build one custom site per year where time isn't a constraint
  • You handle all content updates yourself
  • Your clients are technical enough to use a full page builder safely

There's no right answer for everyone. Just different priorities.

The Component Library Approach

Instead of giving clients a blank canvas, you give them a curated toolkit.

A typical TheDock site might export with these components:

  • Hero section (headline, subheading, CTA)
  • Two-column content (text + image, swappable)
  • Testimonial block (quote, name, photo)
  • Image gallery (upload multiple images)
  • CTA section (headline, button)

Clients build pages by stacking these components. They can reorder them, fill in content, upload images. But they can't change margins, break the grid, or accidentally delete columns.

It's not limiting—it's curated. Like giving someone a professional kitchen instead of a chemistry lab.

Real Example: Before and After

Before TheDock (manual ACF approach):

Building a hero section component:

  1. Create ACF field group (20 minutes)
  2. Add fields: headline, subheading, background image, CTA text, CTA link (15 minutes)
  3. Write PHP template to render the fields (30 minutes)
  4. Write CSS for layout and styling (45 minutes)
  5. Test responsive behavior (20 minutes)
  6. Debug edge cases (30 minutes)

Total: ~2.5 hours for one component

With TheDock:

  1. Design the hero section visually (20 minutes)
  2. Mark which elements are editable (5 minutes)
  3. Export (generates ACF fields + template automatically)

Total: ~25 minutes for the same component

The second component takes even less time because you're using the same design system.

What Gets Exported

When you export a TheDock site, you get a WordPress child theme with:

PHP files:

  • Template parts for each component
  • ACF field definitions (importable JSON)
  • Standard WordPress template hierarchy

CSS:

  • Component styles
  • Responsive breakpoints
  • Design system variables

Assets:

  • Images and media
  • JavaScript (if used)

No TheDock-specific code. No dependencies. Just standard WordPress architecture that any developer can maintain.

The ACF Ecosystem

TheDock uses Advanced Custom Fields because it's the industry standard for structured content in WordPress.

Over 2 million active installs. Maintained since 2011. Most agencies already know it.

If you stop using TheDock, your content remains in ACF fields. You can:

  • Continue using the exported theme indefinitely
  • Migrate to another ACF-based setup
  • Have any WordPress developer maintain it

This isn't theoretical. We've handed off dozens of sites where clients asked: "What if we don't want to use TheDock anymore?"

The answer: Nothing changes. You already have the exported theme.

When Custom Code Still Wins

TheDock won't replace custom development for everything.

If you need:

  • Highly complex interactive components
  • Custom JavaScript functionality
  • Integrations with external APIs
  • Unique animations or effects

You'll still write code. TheDock handles the 80% of components that follow common patterns—content sections, image galleries, testimonials, CTAs.

The goal isn't to eliminate code. It's to reduce the tedious parts so you can focus on what's actually unique.

The Training Problem

Traditional page builders require training.

When you hand off an Elementor site, you need to:

  • Explain sections vs. containers
  • Show how to duplicate elements
  • Warn about what not to change
  • Create documentation
  • Schedule a training call

With TheDock's exported components, training is simpler:

"See these sections? You can add more by clicking the plus. Fill in the fields. Don't worry—you can't break the layout."

Most clients understand this immediately because it's just WordPress blocks with custom fields.

What This Isn't

This isn't:

  • A replacement for Gutenberg (it works alongside it)
  • A visual builder for clients to use (they use ACF fields)
  • A no-code solution (you still need development knowledge)
  • Suitable for DIY site builders (it's for professionals)

TheDock is a tool for developers and agencies who want to:

  • Build ACF-based sites faster
  • Give clients a safer editing experience
  • Export to native WordPress themes

The WordPress Core Question

"Why not just use Gutenberg?"

Gutenberg is improving. Block patterns and variations are getting better. If you're building sites for technical users who understand WordPress, Gutenberg might be enough.

The difference:

  • Gutenberg is flexible by design. Clients can install plugins, change settings, add arbitrary HTML.
  • ACF Flexible Content is constrained by design. Clients can only use the components you created.

Some agencies prefer the flexibility. Others prefer the control. Neither is wrong—just different trade-offs.

Final Thought

After 15 years building WordPress sites, we've learned that the best client experience isn't unlimited freedom.

It's carefully designed constraints.

Not because we don't trust clients. But because their job is running their business, not mastering web design tools.

TheDock lets you design those constraints visually instead of coding them from scratch.

If you're building custom WordPress sites for clients and spend hours on ACF setup, this might save you time.

If you prefer full page builders or enjoy coding everything manually, that's fine too.

Different tools for different workflows.

Try TheDock for free

TheDock is free for self-hosted WordPress-sites. Sign up, download and get started.

If you do not have a server, you can test on ours; no credit card required. Build, publish and inspect the result, from front-end to back-end to source code. It is all yours and free to edit as you like.

More Reading