TheDock Enhanced Rich Text Editor serves as a sophisticated WordPress classic editor replacement, offering seamless integration with the WordPress TinyMCE 6 editor and enhanced functionality through TinyMCE 6 ACF integration, making it an essential rich text editor plugin for developers and content creators alike. TheDock Enhanced Rich Text Editor represents a significant advancement in document editing technology, offering users a sophisticated platform for creating and formatting text with ease. This tool is designed to enhance productivity by providing a user-friendly interface and a comprehensive set of features tailored for both professional and personal use. With its robust functionality, TheDock streamlines the editing process, ensuring that users can produce high-quality documents efficiently. This innovative solution is poised to redefine the standards of rich text editing in various applications. TheDock Enhanced Rich Text Editor presents an advanced solution for content creation that combines user-friendly functionality with robust features. This editor is designed to facilitate seamless text formatting, allowing users to produce professionally styled documents with ease. Its intuitive interface and comprehensive toolset enhance productivity, making it an indispensable resource for professionals seeking to elevate their written communication. TheDock stands at the forefront of rich text editing, ensuring a superior editing experience.
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:
The alternative isn't removing their access. It's designing what they see in the first place.
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.
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:
A typical agency site might have 15-20 components. That's days of development before you can show the client anything.
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 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.
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.
This approach makes sense if:
It probably doesn't matter if:
There's no right answer for everyone. Just different priorities.
Instead of giving clients a blank canvas, you give them a curated toolkit.
A typical TheDock site might export with these components:
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.
Before TheDock (manual ACF approach):
Building a hero section component:
Total: ~2.5 hours for one component
With TheDock:
Total: ~25 minutes for the same component
The second component takes even less time because you're using the same design system.
When you export a TheDock site, you get a WordPress child theme with:
PHP files:
CSS:
Assets:
No TheDock-specific code. No dependencies. Just standard WordPress architecture that any developer can maintain.
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:
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.
TheDock won't replace custom development for everything.
If you need:
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.
Traditional page builders require training.
When you hand off an Elementor site, you need to:
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.
This isn't:
TheDock is a tool for developers and agencies who want to:
"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:
Some agencies prefer the flexibility. Others prefer the control. Neither is wrong—just different trade-offs.
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: Download
It's free for self-hosted WordPress. Build a component, export it, see the ACF field definitions and template files. Then decide if this approach fits your workflow.
When you choose a WordPress page builder, you're making two decisions:
Most people only think about the first one.
The second decision matters more. Not immediately—maybe not for a year or two—but eventually, when your needs change or a better tool comes along.
By then, if you've built 50 pages, the architecture choice has already been made for you.
Some builders store content in ways that let you leave cleanly. Others don't. That difference isn't accidental—it's a business model.
When you choose a page builder, you're not just choosing a tool. You're choosing how easy it will be to leave later.
Some builders store content in standard HTML. Remove the plugin, and your site still works.
Others use proprietary formats. Remove the plugin, and your pages break. Your content is functionally trapped.
Neither approach is inherently wrong. But the difference matters, especially after you've built 50 pages.
McKinsey research found that B2B companies with strong lock-in strategies achieve 13% higher revenue growth compared to industry peers. For software companies, that's significant.
Lock-in is a business model. And like any business model, it has trade-offs for both sides.
Industry data shows that SaaS churn rates vary widely based on switching costs:
That difference compounds. A customer who stays twice as long is worth roughly twice as much.
For a subscription product, that's the difference between sustainable and struggling.
Page builders that make migration difficult benefit from this dynamic. Not because they're evil, but because it's economically rational.
The harder it is to leave, the longer customers stay—even if they're unhappy.
Not all lock-in is created equal. After working with dozens of WordPress sites, we've seen three distinct patterns:
What it is: Content stored in proprietary formats, not because of deliberate strategy, but because of how the tool was originally built.
Example: Early WordPress builders like Visual Composer used shortcodes because that was the simplest implementation at the time.
Migration difficulty: Moderate to high. You can extract content, but it requires manual cleanup or custom scripting.
Typical cost: $500-$2,000 for a small site, depending on how many pages you have.
What it is: Architecture specifically designed to increase switching costs as a competitive moat.
Example: Builders that store content in custom post meta fields using proprietary JSON structures. Export is technically possible, but deliberately not supported.
Migration difficulty: High. Often cheaper to rebuild from scratch than migrate.
Typical cost: $2,000-$10,000+ depending on site complexity.
What it is: Your entire workflow built around one vendor's ecosystem—builder, hosting, add-ons, integrations.
Example: Full platform stacks where everything works together seamlessly, but only within that platform.
Migration difficulty: Extremely high. You're not just changing a tool, you're changing your entire workflow.
Typical cost: Often requires complete rebuild. Costs vary wildly.
Here's the uncomfortable truth: lock-in isn't always bad.
If you're using Elementor's full stack—builder, cloud, hosting, add-ons—and everything works well for you, the integration value might outweigh the migration risk.
That's a choice, not a trap.
The problem isn't lock-in itself. It's accidental lock-in—when you don't realize you're locked in until you try to leave.
After building WordPress sites for 15 years, we've seen the pattern repeat: tools get abandoned, companies shut down, pricing changes force migrations.
The sites that survive these changes are the ones built on standards, not proprietary formats.
TheDock exports to native WordPress themes because we believe your content should outlive our software.
When you export a TheDock site, you get:
Disable TheDock and your site keeps working. Because it's not a TheDock site anymore—it's a WordPress site.
If you're using a page builder, here's a simple test:
1. Disable the plugin on a staging site
Look at your content pages. Are they:
2. Export your content (Tools → Export in WordPress)
Open the XML file. What do you see?
<p> and <h2>? (Low risk)[vc_row]? (Medium risk)3. Count your pages and do the math
Rough migration costs based on builder complexity:
If you have 100 pages and migration would cost $5,000, ask yourself: is that more or less than 3 years of subscription costs?
Some software companies compete on trust instead of lock-in.
WordPress itself doesn't trap your content. You can export and move to another CMS anytime. Has that hurt WordPress adoption? No—it's the most popular CMS in the world.
Stripe didn't build switching costs into their payment API. They compete on quality and developer experience. They're one of the most valuable fintech companies.
The bet is simple: if your product is good enough, people won't want to leave. And if they know they can leave easily, they're more likely to commit.
That's the bet we're making with TheDock.
We don't have venture capital demanding 10x growth. We don't need to maximize lifetime value through switching costs. We'd rather earn retention through quality than enforce it through architecture.
Will that make us as big as Elementor? Probably not.
But we're okay with that trade-off.
The financial cost of migration is obvious. But there are hidden costs:
Decision paralysis: "We know this isn't optimal, but switching is too expensive."
Strategic limitation: "We'd like to try that new approach, but our current tool can't handle it and we can't switch."
Opportunity cost: Time spent on migration instead of growing your business.
Anxiety: "What if they raise prices 10x? What if the company shuts down? We're stuck."
Lock-in isn't just about money. It's about control over your own infrastructure.
The best software doesn't trap you. It works well enough that you don't want to leave.
TheDock might not be the fanciest builder. It might not have the biggest template library or the most features.
But you'll always own your content. You'll always be able to leave.
And if we do our job right, you won't want to.
Try TheDock: Download
It's free for self-hosted WordPress. No credit card required. Build something, export it, see the actual theme files. Then decide if exportability matters to you.
Three years ago, we watched a talented designer spend two hours configuring spacing on a contact form.
Not designing it. Configuring it.
Padding values. Margin adjustments. Responsive breakpoints. Border radius tweaks. The form looked fine after 20 minutes. The next 100 minutes were perfecting decisions that didn't matter to her client or their customers.
She wasn't slow. She wasn't inexperienced.
She was trapped in a tool that demanded she make a thousand decisions that should have already been made.
That moment became the seed of TheDock. But this isn't a product pitch. It's a conversation about something broken in how we build for WordPress—and why most "solutions" miss the point.
Here's a pattern you've probably lived:
Year 1: Client launches. Site looks great. Everyone's happy.
Year 2: Client calls. "The builder plugin needs updating but it breaks the site. Can you fix it?"
Year 3: Client calls again. "We need a redesign. The site feels old, and our developer says we're locked into this page builder. What do we do?"
You've had this conversation. Maybe multiple times this year.
The website wasn't broken. The business didn't pivot. The design wasn't outdated.
The builder made promises it couldn't keep long-term.
When we started building WordPress sites in 2009, "free" meant something.
Open source. Community-driven. Download it, use it, build with it. No asterisks.
Now "free" often means:
We're not naive about business models. TheDock charges for premium features. We need revenue to keep building.
But here's what bothers us: most "free" builders cripple the tool to force the upgrade. You can't build something professional without paying. The free tier exists to frustrate you into opening your wallet.
We took a different approach.
TheDock's core builder is free. Actually free. No watermarks, no artificial limits, no "pro" features that should be standard.
Why? Because we remember when the web felt open. When anyone with an idea and some determination could build something real.
That version of the internet is worth protecting, even if it's not the most profitable path.
Let us tell you about Sarah.
Sarah ran a design agency. Smart, talented, built beautiful sites for clients. She used Elementor—not because it was perfect, but because it was popular, well-supported, and her team knew it.
Then a client wanted to migrate away from WordPress.
Simple request. Reasonable, even. They'd outgrown their needs, wanted to move to a headless CMS. Sarah said "no problem"—until she tried to export the content.
Three years of blog posts, case studies, and landing pages.
All trapped in Elementor's proprietary shortcode format.
Stripping out the Elementor markup without breaking everything took her team 40 hours of manual work. She couldn't bill for it. The client was frustrated by the delay. Sarah lost money and nearly lost the client.
That's not a bug. That's the business model.
When your content lives in proprietary formats, you're not just using a tool. You're renting your own website from the plugin developer.
Remove the plugin? Site breaks.
Stop paying? Site breaks.
Want to migrate? Pain.
Most builders won't tell you this up front. They show you how easy it is to get started. They don't show you how hard it is to leave.
After watching too many Sarahs—talented professionals trapped by their tools—we asked a different question:
What if the builder was optional from day one?
Not "you can remove it later if you manually migrate everything."
Optional. As in: disable the plugin, site keeps working.
That became TheDock's core principle.
We're a WordPress theme, not a plugin. You build visually, then export creates a real WordPress child theme—actual PHP files, CSS, JavaScript. Standards-compliant code.
Disable TheDock after export? Your site doesn't care. It's running on native WordPress theme code now.
This isn't marketing. It's architecture.
We've handed off dozens of sites where clients asked: "What happens if we stop using TheDock?"
The answer: Nothing. Your site keeps working. You own the code.
That question shouldn't be scary. But with most builders, it is.
Here's what nobody tells you about unlimited customization:
It's exhausting.
Every blank canvas is hundreds of micro-decisions:
By project's end, you've made thousands of decisions. Most of them identical to your last three projects.
Our agency clients—before TheDock—spent 30-40% of project time on setup and configuration. Not design. Not content. Configuration.
That's days of billable time making the same spacing decisions you made last week.
Unlimited freedom sounds empowering. In practice, it's decision fatigue.
When we say "smart defaults," people assume we mean limitations.
We don't.
We mean making the boring decisions so you can focus on the interesting ones.
Typography hierarchy that follows best practices? Done.
Spacing scale that works across breakpoints? Done.
Responsive behavior that doesn't need tweaking? Done.
Want to override any of it? You can. Every default is customizable.
But most projects don't need custom spacing systems. They need good spacing, applied consistently, so you can focus on what makes this client's site unique.
Here's the real difference:
Traditional builder: "Configure everything from scratch every time."
TheDock: "Start with something proven. Customize what matters."
One approach treats every project like it's the first website ever built.
The other respects that you've done this before.
In 2006, Twitter launched with a 140-character limit.
Critics said it was too restrictive. "Who can express anything meaningful in 140 characters?"
Turns out, everyone.
That constraint didn't limit expression. It defined a new medium. It forced clarity. It created a unique voice that wouldn't have existed without the boundary.
Instagram did the same with square photos. Constraints that felt limiting became defining features that made the platform valuable.
TheDock's smart defaults work the same way.
We're not taking away your freedom. We're giving you a framework that makes decisions easier, sites more consistent, and handoffs cleaner.
Constraints don't limit creativity.
They channel it.
We've built WordPress sites since 2009. Hundreds of them. For clients ranging from solo bloggers to international brands.
Here's what we've learned matters long-term:
Trends change. Plugins get abandoned. Companies get acquired and shut down.
Your content should survive all of it.
If your blog posts are trapped in shortcodes that only work with one specific plugin, you don't own your content. You're borrowing it.
TheDock stores content in standard WordPress formats. Posts, pages, custom fields—ordinary HTML. No proprietary markup.
Because your words should outlive our software.
WordPress core (Gutenberg) will be here. It's the platform.
Elementor probably will too. They have funding, market share, momentum.
But that new "AI-powered, blockchain-integrated, revolutionary" builder? Maybe not.
We can't predict the future. But we can build on standards that have survived the past 15 years.
Here's a conversation every agency has had:
Client: "I tried to add a section and now the whole page is broken. Can you fix it?"
You: "What did you change?"
Client: "I don't know. I just dragged something."
With unlimited freedom comes unlimited ways to break things.
TheDock gives clients a curated experience. They can edit content, create pages, customize sections—but they're building from pre-designed components that maintain structure.
They get creative freedom. You get peace of mind they can't accidentally destroy the layout.
Let's be honest about who this is for.
TheDock is great if you:
TheDock probably isn't right if you:
We're not for everyone. Elementor serves millions of users successfully. Gutenberg is improving rapidly. Webflow is powerful for the right projects.
There's no one "correct" answer. Just different priorities.
Ours are: standards, portability, and respect for your time.
What are yours?
Quick story: Klarna didn't win payments by having more features than competitors.
They won by making checkout smoother.
"Smooth payments" became their position. Competitors had features. Klarna had a better experience.
TheDock's position is similar: smooth WordPress productivity.
Other builders compete on widget counts and template libraries.
We compete on workflow efficiency.
You'll build great sites with any tool. This way is just smoother.
TheDock started as an internal tool.
We were bouncing between Visual Composer, ACF field groups, and Elementor—building the same components repeatedly, configuring the same settings, solving the same problems.
We wanted something that didn't exist:
A visual builder for WordPress that outputs clean, native code. No lock-in. No proprietary cruft. Pre-configured for speed but customizable when needed.
So we built it.
The team behind TheDock includes the creator of Uncode (133,000+ sales, one of ThemeForest's top themes). We've been building WordPress themes for 15 years. This isn't our first attempt at solving builder problems.
What we built:
Full disclosure: We have biases. We built this for how we work. It might not match how you work.
But if you've felt the friction of traditional builders—decision fatigue, client handoffs that require training manuals, lock-in anxiety—TheDock might make sense.
People ask how we compare to Elementor.
Here's the truth: Elementor is successful for good reasons.
Why we built something different:
But here's what matters: For many people, Elementor's trade-offs are acceptable. Large ecosystem, easy onboarding, lots of support.
We prioritize differently. That doesn't make one right and one wrong. Just different choices for different needs.
If this philosophy resonates, try TheDock on a real project.
You'll know within the first hour if opinionated workflows match how you work.
It's free for self-hosted WordPress. No credit card, no trial period, no feature restrictions. Just the builder we wish existed when we started.
If it doesn't fit your workflow, no hard feelings. Uninstall it, move on. We won't email you asking why you left.
But if you've been looking for something like this—a visual builder that respects WordPress standards and doesn't trap your content—we're here.
TheDock has no external investors. It's owned by the people who built it.
This isn't marketing department copy approved by a committee. It's what we actually think after 15 years building WordPress sites.
We're not trying to replace Elementor. We're building for the people who want something different—and we're willing to be smaller, more focused, and less universally appealing to serve them well.
If you want to talk WordPress, theme architecture, or why we're still obsessed with Dieter Rams' design principles, we're around.
Email us. We answer.