5 Features That Make WordPress Great 2026
WordPress remains the dominant CMS in 2026 — the block editor and Full Site Editing have matured, the plugin ecosystem is massive, and it's still free and open-source, though the 2024-25 WP Engine dispute shook community trust.
Every Wednesday. 28,400+ operators. Zero fluff.
✓ Check your inbox — click the confirmation link to complete sign-up.
✓ You're subscribed!
✓ You're already on the list.
Table of contents
Open Table of contents
- 1. The Block Editor (Gutenberg) Has Grown Up
- 2. Full Site Editing Changes What “Theme” Means
- 3. Performance: Much Better, Still Requires Attention
- 4. Security: Solid Core, Weakest Link Is Plugins
- 5. The Plugin Ecosystem: 60,000+ and Counting
- The WP Engine Controversy: What You Need to Know
- Bottom Line
- WordPress — 2026 FAQ
- The shorter version
- Updated for May 2026
1. The Block Editor (Gutenberg) Has Grown Up
The early Gutenberg editor (launched in 2018) was rough and controversial. By 2026, it’s a genuinely capable block-based editor that rivals Webflow for layout flexibility — without the vendor lock-in.
Every element on the page is a “block”: paragraphs, images, buttons, columns, embeds. You drag, stack, and configure them visually. No shortcodes, no page-builder plugins required for most use cases. The editor works the way you’d expect a modern tool to work.
For teams: the block-locking feature lets you create templates where certain blocks are editable and others are locked — useful if you’re handing a site to a non-technical client.
2. Full Site Editing Changes What “Theme” Means
Full Site Editing (FSE) arrived in WordPress 5.9 and has matured considerably since. It means the block editor now controls not just post content but headers, footers, sidebars, and page templates — everything.
Block themes (built for FSE) replace the old PHP template system with block-based templates you can edit visually. You no longer need to touch a theme’s PHP files to change where the navigation appears or how the footer is structured.
This is a fundamental architectural shift. If you’re evaluating WordPress and the last time you used it was pre-2022, you’re evaluating a different product.
Classic themes still work — WordPress has strong backward compatibility — but new projects should default to block themes unless there’s a specific reason not to.
3. Performance: Much Better, Still Requires Attention
WordPress has historically carried a reputation for being slow. That’s improved. Core Web Vitals are now a first-class concern for the WordPress core team. Recent versions ship with:
- Native lazy-loading for images
fetchpriorityattributes on above-the-fold images- Reduced JavaScript in the default installation
- The Interactivity API (replaces jQuery-heavy patterns with a lighter runtime)
That said, performance still depends heavily on your hosting, your theme, and — especially — your plugins. A bloated plugin stack can undo all the core improvements. I’d recommend auditing your plugin list quarterly and testing Core Web Vitals in PageSpeed Insights after every significant change.
Good managed WordPress hosts (verify current options and pricing before committing) handle server-side caching, edge CDN, and PHP tuning for you, which removes the biggest variables.
4. Security: Solid Core, Weakest Link Is Plugins
WordPress core is actively maintained. The security team responds quickly to vulnerabilities, and auto-updates for minor releases are on by default. For most sites, the security posture of WordPress core itself is reasonable.
The real attack surface is plugins and themes. Nulled (pirated) themes are a common malware vector. Abandoned plugins with unpatched CVEs are another. Standard practice:
- Keep WordPress, themes, and plugins updated (auto-updates help)
- Remove plugins you don’t use
- Use a reputable security plugin (verify which ones are actively maintained as of your install date)
- Use a managed host that offers malware scanning
Two-factor authentication for admin accounts is non-negotiable in 2026.
5. The Plugin Ecosystem: 60,000+ and Counting
WordPress has more than 60,000 plugins in the official directory, covering everything from SEO (Yoast, Rank Math) to e-commerce (WooCommerce) to forms, membership, and analytics. Most are free. Premium tiers exist for advanced features.
This is WordPress’s deepest moat. No other CMS comes close in plugin breadth.
The caveat is quality control. The official directory has plugins ranging from excellent to abandoned-since-2019. Before installing: check the last updated date, active install count, and recent reviews. A plugin with 100,000 active installs and updates from last month is a different proposition than one with 200 installs and no update in three years.
For theme discovery, Envato Elements remains a solid source for premium block-compatible themes.
The WP Engine Controversy: What You Need to Know
In late 2024, Matt Mullenweg publicly accused WP Engine (a major managed WordPress host) of profiting from WordPress without contributing adequately to the project. The dispute escalated to WP Engine being temporarily barred from WordPress.org infrastructure, including the plugin update feed — meaning WP Engine-hosted sites briefly couldn’t receive plugin updates through the normal channel.
The dispute was eventually addressed through legal and community channels, but it raised a fair question: what does “open source” governance actually protect you against?
The short answer: WordPress the software (licensed under GPL) is not at risk. Anyone can fork it, self-host it, or use it commercially. What happened was a conflict between commercial interests and the WordPress.org platform (controlled by Automattic/Mullenweg), not a threat to the software itself.
If you’re building on WordPress, the governance lesson is: don’t be fully dependent on a single host’s proprietary stack. Keep your own backups. Use the standard WordPress.org plugin directory. Maintain the ability to migrate.
Bottom Line
WordPress in 2026 is a mature, capable platform that has genuinely modernized. The block editor and FSE have closed the gap with proprietary page builders. Performance and security have improved at the core level. The plugin ecosystem is unmatched.
The WP Engine dispute introduced legitimate questions about governance, but the software itself is stable and the GPL license protects end users. For content-heavy sites, blogs, and WooCommerce stores, WordPress remains my default recommendation.
For sites where you want zero maintenance overhead and don’t need a plugin ecosystem, consider whether a static site generator or a more opinionated CMS fits better — those are genuinely better choices for some use cases.
I’ve been using WordPress for years across multiple projects and it keeps earning its place in the stack.
WordPress — 2026 FAQ
Is WordPress still worth using in 2026?
Yes, for most content sites, blogs, and e-commerce stores built on WooCommerce. The block editor and Full Site Editing have matured, the plugin ecosystem is the largest in the industry, and GPL licensing means you’re never locked in. If you need zero maintenance, a static site generator may suit you better.
What’s the difference between WordPress.com and WordPress.org?
WordPress.org is the open-source software you download and host yourself — fully customizable, free. WordPress.com is Automattic’s hosted service built on that software, with tiered pricing and some restrictions on plugins at lower tiers. When people say “WordPress,” they usually mean WordPress.org; verify current WordPress.com plan limits before committing to a hosted plan.
How did the WP Engine controversy affect WordPress sites?
It mainly affected WP Engine-hosted sites, which briefly couldn’t receive plugin updates through the standard WordPress.org channel. The underlying WordPress software was not affected. If you’re self-hosted or on a different host, the dispute had no direct impact on your site.
What’s Full Site Editing and do I need it?
Full Site Editing (FSE) lets you edit headers, footers, templates, and page layouts using the same block editor you use for post content — no PHP required. It’s a significant shift from classic themes. New projects should default to block themes that support FSE; existing classic-theme sites can continue without FSE, but FSE is the direction WordPress is heading.
Related reading: History of blogging · What is SEO · Create a million-dollar e-commerce business
The shorter version
If you’re reading this because the workflow it describes is eating your week, that’s the kind of loop I build AI agents for. Two build slots open at a time.
Updated for May 2026
A short note from May 2026: the workflow this post describes was checked against the current state of the underlying tools and platforms. Where specific tools, UIs, or features have evolved, the structural advice still holds — the implementation will look slightly different in 2026. If you hit a step that doesn’t match what you see on screen, that’s likely a UI refresh, not a fundamental change in approach. Drop a note via the contact form and I’ll patch it explicitly.
Every Wednesday. 28,400+ operators. Zero fluff.
✓ Check your inbox — click the confirmation link to complete sign-up.
✓ You're subscribed!
✓ You're already on the list.
Get the AI playbook in your inbox
Every Wednesday. 28,400+ operators. Zero fluff.
Check your inbox.
We sent you a confirmation email — click the link inside to complete your subscription. Check spam if you don't see it within a minute.
You're subscribed.
Welcome — the next edition lands in your inbox soon.
You're already on the list — look for it every Wednesday.