Key Takeaways: You bounced on the block editor in 2022, and honestly? Fair. But 2025 isn't 2022. While the Site Editor has matured, three massive architectural gaps remain: native mega menus, dynamic conditional display, and a frictionless ACF-style field UX. Page builders are doubling down on these exact holes. Here is an honest audit of why they still matter and when to stick with a hybrid stack.
You tried Gutenberg in 2022. It felt like typing inside a moving train. You went back to Elementor or Divi, closed the tab, and didn't look back. Now it's 2025, and your agency is pushing you toward “native block themes” to save on licensing fees. Before you delete your page builder, take a breath.
WordPress has grown up, but it hasn't grown a complete brain yet. There are three specific patterns where the block editor still hits a brick wall, and ironically, these are the exact three battlegrounds where page builders are placing their biggest 2025 bets.
The Navigation Nightmare: Why Mega Menus Still Break Blocks
The WordPress Navigation block works fine for a list of links. It fails spectacularly when you need a “Mega Menu.” You know, the kind with images, featured products, or multi-column layouts inside the dropdown. Core WordPress treats navigation as a simple hierarchy of links. It refuses to acknowledge that modern e-commerce and SaaS sites need content-heavy navigation.
Why does this matter? Because navigation is the highest-traffic real estate on your site. If you can't put a “Latest Blog Post” or a “Promo Banner” inside your menu without hacking PHP templates, you aren't building a modern site; you are building a brochure.
Page builders like Elementor and Divi know this. They have spent the last six months refining their “Nested Sections” inside menus. They bet that if you can't control your header visually in core, you'll pay $89/year for the builder that lets you.
Conditional Display: The “If/Then” Logic Core Ignores
This is the silent killer of block-based sites. In a page builder, you can click a block, go to “Advanced,” and set a condition: “Only show this block if the User is Logged In,” or “Only show this if Post ID is 42.”
The block editor has zero native support for this. If you want to show a “Login to Download” button instead of a “Download Now” button, you currently have to write custom PHP logic or buy a plugin like Conditional Blocks. For a developer, this feels like a step backward to the shortcode era.
This lack of logic makes building complex landing pages (where elements react to user state) nearly impossible without a third-party dependency. Page builders win here because they treat the “render engine” as a product feature, not a core responsibility.
The Custom Fields UX: The ACF Factor
Advanced Custom Fields (ACF) changed the game. But let's be real: the “Block Bindings” API in WordPress core is still developer-territory. It requires JSON configuration and technical setup. ACF's “Flexible Content” field lets you build complex data structures in a drag-and-drop interface that clients actually understand.
Builders are betting on this hard. They are integrating AI to generate these field structures automatically. If you are building a site for a client who needs to manage complex data (like a real estate listing or a recipe database), the block editor's current native field experience is too abstract for a non-technical user.
The “Anti-Fragile” Framework: When to Stay Hybrid
You don't need to choose a side. You need a framework. I call it the “Anti-Fragile” stack. If your project hits any of these three criteria, stop trying to force a pure block theme and embrace the hybrid approach.
- The “Client-Managed” Mega Menu: If the marketing team needs to change a promo banner inside the nav menu weekly, do not hand them PHP code. Hand them a Builder Nav.
- The “State-Dependent” Landing Page: If your conversion funnel relies on showing different elements to logged-in vs. anonymous users, stick with a builder that has a conditional logic engine built-in.
- The “Data-Heavy” Post Type: If you have 15+ custom fields per post, ACF Pro inside a builder is still faster and more reliable for client hand-off than raw Block Bindings.
Related Reading: Check out Block Themes ARE FSE to see where the native editor actually excels, or read our Page Builder Bill Audit to see if you are overpaying for features you don't use.
Conclusion: The Maturity Gap is Real, but Shrinking
The block editor is no longer the beta product it was in 2022. It is a capable, fast, and SEO-friendly foundation. However, the “three patterns” gap shows us that WordPress core prioritizes the 80% use case. If you build complex, data-driven, or logic-heavy sites, the remaining 20% is where page builders will keep winning for at least another 18 months.
Don't ditch your tools because of a trend. Ditch them when the core can actually do the job better.
Frequently Asked Questions
Will the block editor ever get native Mega Menus?
Not in the traditional sense. WordPress core philosophy favors simple, accessible navigation. While the Navigation block will continue to improve for basic links, the “content-heavy” mega menu is viewed as a “theme territory” or “plugin territory” feature by core contributors. Expect to see third-party blocks filling this gap, but not a native core feature soon.
Is ACF dead now that Block Bindings exist?
No. Block Bindings is an API for developers to map data to blocks; it is not a user-facing UI. ACF provides the UI that clients use to manage data. In 2025, ACF (now owned by WP Engine) is actually more powerful because it can use its own UI to feed data into the native Block Bindings API. It's a layer, not a competitor.
How do I handle conditional display without a page builder?
You currently have two choices: use a dedicated plugin like “Conditional Blocks” which adds a UI for logic, or write custom PHP using the render_block filter. The latter is more performant but requires coding knowledge. For most agencies, a lightweight plugin is the stopgap until core addresses this.
Are hybrid WordPress stacks (Blocks + Builder) a performance risk?
They can be. Mixing builders with block themes often leads to “CSS bloat,” where both systems try to load their styles. To mitigate this, use a “Performance” builder like Spectra or GenerateBlocks that respects core standards, rather than heavy legacy builders like Divi or Elementor, if speed is your primary concern.
