Hey, Simone here. If you’ve ever side-eyed WordPress’s block editor, believe me, I’ve been there. When it dropped in 2018, I was the one hugging the classic editor plugin like a security blanket. But a few years—and a pile of client projects—later, I’ve flipped. The block editor isn’t just tolerable. It’s honestly good. The noise you hear is mostly old gripes and a stubborn refusal to give it another look. So I’m going to walk you through why I think the block editor is better than people say, no sugarcoating, just real talk from the trenches.
The Rocky Start That Still Haunts It
Let’s not kid ourselves: the block editor’s debut was a mess. WordPress 5.0 shoved Gutenberg into the world, and it felt like a beta test nobody signed up for. Clunky interface. Missing keyboard shortcuts. Workflows that crumbled on contact. I can still feel the frustration of trying to line up a couple of columns for a landing page and burning an hour on nonsense. That first year left a scar, and I don’t blame anyone who wrote it off back then.
But here’s the part people keep forgetting: that was over five years ago. The editor has been hammered on, update after update. The version sitting in your dashboard today is slicker, quicker, and way more predictable. Yet the 2018 reputation hangs around like stale smoke. When I chat with other freelancers, their complaints often point to bugs or quirks that got squashed ages ago. It’s like judging a high schooler for something they did in kindergarten.
The classic editor was cozy, sure. But cozy isn’t the same as capable. And the block editor, despite its early face-plants, has grown into a tool that actually fixes problems the old way never touched. If you haven’t kicked the tires lately, you might be shocked.
What the Block Editor Actually Gets Right
Enough history. Let’s talk about what’s working right now. I’m not going to pretend it’s flawless—nothing is—but there are some real wins here that get buried under the complaints.
It Makes Layouts Truly Visual
With the classic editor, you’d type out text, maybe plop in an image, and cross your fingers the alignment wouldn’t implode. Want a multi-column section? You were either hand-coding HTML or bolting on a page builder that turned your site into a whale. The block editor flips that script. Every piece of content becomes a block you can shift, style, and arrange while you watch.
I can tug a paragraph next to an image, stack a testimonial between two buttons, or slap together a full-width cover section without typing a single angle bracket. For someone who doesn’t think visually by default, that’s massive. I’m not squinting at a preview tab, guessing if the spacing works. I just see it. That alone saves me hours on a typical project.
And it’s not all about columns. The group block lets me nest stuff. The spacer block gives me consistent breathing room. Reusable blocks? I can save a pattern once and drop it anywhere. My portfolio site has a “project spotlight” section I reuse across pages. In the classic editor, I’d copy-paste raw HTML and pray I didn’t fumble a closing tag. Now it’s two clicks and done.
It Plays Nicer with Themes and Plugins
One of the biggest headaches with old-school page builders—looking at you, Elementor and Divi—was lock-in. You’d craft a gorgeous site, switch themes, and suddenly your layouts were a graveyard of broken shortcodes. The block editor, baked right into WordPress, sidesteps that trap. Your content stays clean and portable.
I’ve hauled several client sites off page builders and onto the block editor, and the speed bump alone was worth the sweat. Those drag-and-drop beasts load a mountain of JavaScript and CSS, even for features you’re not using. The block editor stays lean, only loading assets for the blocks you actually drop in. My own blog crawled along at 3.2 seconds; after I kicked the page builder to the curb, it clocked under 1.5. That’s not just a nerd stat—it’s a better experience for visitors and a quiet SEO boost.
Theme compatibility has grown up, too. Most modern themes ship with block editor styles and full-site editing support. I run a lightweight block theme, and tweaking headers or footers no longer means spelunking through the Customizer or a separate theme panel. It’s all one interface. Less bouncing around means fewer mistakes and faster builds.
It Encourages Better Content Structure
Confession: in the classic editor, I got lazy with headings. I’d bold a paragraph instead of wrapping it in an actual H2 because the toolbar buttons were right there. Terrible for accessibility, lousy for SEO, but the editor didn’t nudge me to fix it. The block editor treats every heading as its own chunk with clear hierarchy options. It quietly pushes you toward semantic HTML without wagging a finger.
My writing’s more organized now. The document outline panel sits on the left, showing me the heading structure at a glance, so I catch skipped levels or walls of text that need a break. When I’m deep in a long tutorial, I can collapse sections to stay locked in, and the navigation block auto-builds a table of contents from my headings. I didn’t know I needed that. Now I’d hate to work without it.
On the accessibility front, the block editor handles landmarks and ARIA labels better out of the box. It’s not a magic fix—you still need to test—but it’s a step up from the classic editor’s div soup. As someone who wants my sites usable by everyone, that counts.
The Criticism I Don’t Buy
I’ve heard all the arguments against the block editor. Some are fair. A lot are frozen in time. Let me tackle the ones that make me twitch.
“It’s Too Complicated”
The block editor has a learning curve, no argument. But so does any tool worth picking up. The classic editor was simple because it barely did anything. You typed, dropped in media, hit publish. That’s fine for a plain blog post, but the web has moved on. Readers expect richer layouts, and clients want to steer their own pages without phoning a developer.
What I’ve noticed is that the complexity is mostly a vibe, not a fact. The toolbar tucks away options until you need them, and the block inserter is searchable. When I walked a non-technical client through it recently, fifteen minutes was all it took before she was off and rolling. She actually liked it better than the old TinyMCE interface because she could see what each block did. The classic editor’s trick was hiding everything behind a familiar face—until something broke, and then you were stranded.
If you’re banging your head against it, start with just three blocks: paragraph, heading, image. Ignore the rest. You can build a full post with those. The extra stuff is optional power, not mandatory chaos.
“It’s Too Slow”
Speed complaints were everywhere in the early days, and a sluggish admin is genuinely maddening. But the block editor today is noticeably zippier. I’m on a mid-range laptop, nothing fancy, and I rarely hit lag. Big posts with dozens of blocks might take a beat to load, but that’s on par with any modern editing tool.
If your dashboard is crawling, the real villain is often your plugins and theme, not the editor itself. A sloppy plugin can inject its scripts everywhere and tank performance. I’ve scrubbed sites where killing a single plugin cut editor load time in half. The block editor gets blamed for the neighborhood’s problems, and that’s just not right.
“It Doesn’t Work for Developers”
This one always scratches my head. I’m not a hardcore dev, but I know enough to whip up a custom block when I need to. The block editor exposes a rich API, and the React-based rendering opens doors the classic editor never had. If you’re comfortable with JavaScript, you can build editing experiences tailored to your clients that they can’t accidentally wreck.
For devs who want a text-first workflow, the code editor block and the custom HTML block are still sitting right there. Nobody’s forcing you into the visual interface. And with full-site editing, you can template entire page layouts in theme files while handing content editors a locked-down, safe sandbox. That’s not losing control—that’s leveling up.
Real-World Scenarios Where the Block Editor Shines
Theory is nice, but let me give you a few concrete times the block editor pulled my fat out of the fire.
Landing Pages Without a Page Builder
Last month I needed a quick landing page for a webinar signup. The old me would’ve installed a page builder, grabbed a template, and then burned an hour stripping out bloat I didn’t ask for. With the block editor, I built the whole thing from scratch in under thirty minutes. A cover block for the headline, a columns block for the benefits, a button block for the call to action, and a form block powered by a lightweight plugin. No extra frameworks, no spaghetti code. The page loaded fast and converted well. Done.
Client Handoff Without Headaches
One of my regular clients runs a small bakery and updates her own site every week. Before the block editor, I’d build her pages with a page builder, and she’d call me in a panic every time she accidentally nuked a row. Now I lock down the critical sections with block patterns and templates, and she edits only the content areas I’ve marked. She can swap text, change images, add new posts—without the fear. My support tickets have practically vanished.
Writing Long-Form Content
I’m typing this post in the block editor right now. For marathon writing sessions, focus mode is a gift. It dims everything except the block I’m working on, so the clutter fades. The word count and outline panel keep me honest, and I can drop in a table or a pullquote with a slash command instead of hunting through menus. It’s a writing environment that feels current—not like a fossil from 2010.
A Few Honest Frustrations
I promised no fluff, so I’ve got to mention what still gets under my skin. The block editor isn’t spotless.
First, the mobile experience is mediocre. Editing on a tablet is doable but clumsy, and I wouldn’t wish a complex layout on a phone. If you publish from a mobile device most of the time, the classic editor might actually treat you better right now.
Second, the sheer pile of blocks can be overwhelming. The directory swells constantly, and while that’s great for options, it can feel like standing in a cereal aisle with no labels. I wish the built-in curation tools were sharper.
Third, full-site editing is still finding its feet. It’s powerful, but the interface can confuse, and theme compatibility is a coin toss. I’m cautiously optimistic, but I’m not ditching my current workflow wholesale just yet.
These are real gripes, but they’re not deal-breakers for me. They’re growing pains, not cracks in the foundation.
Why the Hate Persists
So if the block editor is actually decent now, why does the internet keep roasting it? I think it boils down to a few human things.
Change stings. WordPress had a stable, boring editor for over a decade, and people built whole careers around it. When that rug got yanked—with a rough rollout and not much opt-out grace—it felt like a shove, not an invitation. Once you’ve tagged a tool as the enemy, it’s tough to come back with fresh eyes.
Then there’s the echo chamber. Social media and forums amplify complaints. The folks happily using the block editor don’t usually sprint to post about it. I’m guilty of that myself—I’ve been using it for years and never wrote a positive word until now. The loudest voices aren’t always the truest sample.
And I think some people tangle the block editor up with the broader WordPress project drama. The editor became a symbol of top-down decisions, and bashing it turned into a way to push back against Automattic’s influence. That’s a conversation worth having, but it’s separate from whether the tool actually works.
FAQs About the Block Editor
Is the block editor going to replace page builders?
Not completely, and I don’t think it should. Page builders still offer deeper design control and pre-built templates for users who need that. But for a ton of standard sites, the block editor can handle what used to demand a builder. I see them coexisting, with the block editor nibbling away at the low-to-mid complexity space.
Can I still use the classic editor if I want?
Yep, the classic editor lives on as a plugin and is maintained for backward compatibility. You can install it and keep working exactly as you always have. I’d nudge you to try the block editor on a test site, but the old way isn’t vanishing tomorrow.
Does the block editor affect my site’s front-end speed?
It doesn’t inherently drag your site down. Unlike some page builders, the block editor spits out pretty clean HTML and only loads CSS for blocks you’re actually using. A well-tuned block-based site can be quick as a hiccup.
What if I don’t know React—can I still build custom blocks?
You can, but it’s a steeper climb. The modern block API leans on React, so you’d need to pick up some basics. The alternative: build custom patterns out of existing blocks, which takes zero coding. For heavier needs, hiring a developer or using a block-building plugin are solid paths.
Wrapping Up
Here’s the short version: the block editor isn’t the villain people paint it as. It’s a capable, still-growing tool that makes creating content more visual, more structured, and more bendable. I’m not asking you to love it. I’m just asking you to judge it on what it is right now, not what it was when it stumbled out of the gate.
For my own work, the block editor has slashed development time, tightened site performance, and made my clients happier. It’s not glamorous to admit, but sometimes the default option is the right one. Give it a fair shake on a recent version of WordPress, and you might discover—like I did—that the grass is actually greener than the complaints make it sound.
Thanks for reading my unfiltered take. Now go build something cool.