Bottom line: While Gutenberg represents WordPress's future, the Classic Editor combined with Advanced Custom Fields delivers superior results for custom theme development—offering better performance, tighter brand control, and more maintainable code for mission-driven organizations that need their websites to work flawlessly for years.
The Unpopular Opinion That Produces Better Websites
In 2018, WordPress introduced Gutenberg as the new default editor, marking a fundamental shift in how content gets created on the platform. The block-based approach promised flexibility, visual editing, and democratized web design. Seven years later, it's evolved into a powerful system with Full Site Editing capabilities.
So why does FatLab still build custom WordPress themes using the Classic Editor and Advanced Custom Fields?
Because after 20 years of WordPress development and dozens of custom projects for advocacy groups, professional organizations, and nonprofits, we've learned what actually matters: reliability, performance, maintainability, and giving clients exactly what they need—nothing more, nothing less.
This isn't nostalgia or resistance to change. It's a strategic development philosophy built on real-world results.
When a Client Specifically Requests "The Old Way"
Here's a story that captures why this approach matters:
After working with two different development firms on their corporate website, Alex Lucas at Genzeon called with a specific request. We had worked together years earlier at another organization, and his new project was stalled—designs approved, budget spent, but no functional website after months of effort.
His request wasn't just "can you rescue this project?" It was more specific: "I want it built the way you used to do it for me."
What he meant was ACF and Classic Editor. No page builders. No blocks. Just clean, custom WordPress development that works reliably and gives content editors exactly the control they need—nothing more, nothing less.
We rebuilt the entire site in 7-8 weeks. Four different header styles. Mega menu navigation. Responsive animations. Complex design elements that the previous firms couldn't deliver. And most importantly: a content management system that Genzeon's team could actually use without constant developer support.
That project recovery exemplifies why we stick with this approach. When experienced clients have the choice between trendy block-based development and proven ACF architecture, they choose what they know will work.
What We Actually Mean When We Say "Classic Editor Development"
Let's be clear about what we're discussing. We're not talking about giving clients a simple WYSIWYG editor and calling it done. We're describing a complete custom theme development approach:
Classic Editor serves as the content editing interface—a clean, distraction-free environment for writing and updating content without wrestling with blocks.
Advanced Custom Fields (ACF) provides the architecture—custom fields, flexible content layouts, repeaters, relationship fields, and granular control over every element of the theme.
Custom PHP templates handle the presentation layer—where we build exactly the functionality clients need without bloat or unnecessary features.
This combination gives us surgical precision in custom theme development. Every field, every layout option, every piece of functionality exists for a specific purpose. Nothing is there "just in case" or because it shipped with a theme framework.
The Performance Advantage Nobody Talks About
Gutenberg ships with JavaScript dependencies, React libraries, and CSS for every core block—whether your site uses them or not. Page builders like Elementor and Divi make this even worse, loading massive amounts of code on every page load.
Our Classic Editor + ACF approach produces dramatically leaner code:
- No React dependencies loaded on the frontend
- No block editor JavaScript libraries
- No CSS for dozens of block variations you'll never use
- No compatibility layers translating blocks into rendered output
This directly impacts Core Web Vitals, search rankings, and user experience. When we rebuilt Genzeon's website after multiple firms had failed using other approaches, we delivered complex design features—four header variations, mega menus, responsive animations—while maintaining exceptional performance through clean, custom code.
For mission-driven organizations where every visitor matters and mobile users predominate, these performance gains translate to real results.
Brand Consistency That Actually Means Something
Generic themes and block editors give users flexibility. Sometimes that's good. Often it's a liability.
When your organization has established brand guidelines—specific typography, color palettes, spacing systems, image treatments—you don't want content editors accidentally breaking those standards. You need intentional constraints that maintain brand integrity while allowing content updates.
ACF makes this possible. We build custom field groups that present exactly the options clients should have:
- Pre-approved color choices from brand guidelines
- Specific heading hierarchy that maintains accessibility and SEO
- Image fields with proper sizing and cropping for each use case
- Layout options that work within the design system
Content editors can update their sites confidently, knowing they literally cannot break the design. They're not wrestling with block settings or accidentally choosing colors that fail accessibility standards. They're filling in fields we designed specifically for their content.
Through our long-term partnership with Gensler, we've delivered numerous design-driven websites where maintaining the architectural firm's sophisticated visual standards was non-negotiable. ACF-powered custom themes gave them the control they needed.
Maintainability Over the Long Term
Here's what happens with many Gutenberg-based sites: They work great at launch. Six months later, a core WordPress update changes block behavior. A theme update conflicts with a custom block. The client discovers certain blocks don't work reliably on mobile. Now you're maintaining compatibility layers and debugging block rendering issues.
With Classic Editor + ACF development, we control the entire stack:
- Custom fields don't change because we define exactly what they do
- Template logic is explicit rather than depending on block parsing
- Debugging is straightforward because we can see exactly what's happening in the code
- Future developers can understand it because it's PHP templates and custom fields, not proprietary block configurations
The custom learning management system we built for ABFPRS has been supporting medical professionals' board certification for over a decade. That longevity comes from building on stable, maintainable foundations rather than constantly adapting to editor evolution.
When Gutenberg Actually Makes Sense
We're not dogmatic. Gutenberg has legitimate use cases:
Content-heavy sites where editors need layout flexibility. If you're running a news site or magazine where every article needs different layouts, Gutenberg's blocks make sense.
Sites where visual editing is the priority. When clients want to see exactly how content looks while editing, Gutenberg delivers that experience.
Simple sites using core blocks. If a site only needs paragraphs, images, and headings without custom functionality, Gutenberg works fine.
Full Site Editing for appropriate projects. FSE can work well for simpler sites where design flexibility outweighs performance concerns.
But for custom theme development where performance matters, brand consistency is crucial, and the site needs to work reliably for years? Classic Editor + ACF produces better results.
The Real Flexibility Comes from Custom Development
The promise of Gutenberg is flexibility—the ability to create varied layouts without touching code. But that's solving the wrong problem.
When we do custom WordPress development, the flexibility comes from building exactly what clients need:
- Custom post types for their specific content
- Relationship fields connecting related content
- Repeater fields for dynamic sections
- Conditional logic showing/hiding fields based on choices
- Custom admin interfaces that make sense for their workflow
This is architectural flexibility—building systems that work the way organizations actually operate, not just rearranging visual blocks.
For the National Peace Corps Association's 50-site network, we needed sophisticated data relationships, CRM integration, and membership management across multiple domains. That required custom architecture, not a flexible page builder.
Developer Experience That Produces Better Code
Here's something that doesn't get discussed enough: developer experience affects code quality.
With Classic Editor + ACF development:
- We write explicit PHP templates instead of reverse-engineering block output
- We can see exactly what fields exist and how they're used
- Debugging is transparent rather than hunting through block parsing layers
- Version control diffs are readable because we're tracking template changes, not block comment metadata
- New developers can onboard quickly because the architecture is clear
Better developer experience means better code. Better code means more reliable websites. More reliable websites mean fewer support issues and lower long-term costs.
Why This Matters for Mission-Driven Organizations
Nonprofits, advocacy groups, and professional associations can't afford websites that break, slow down, or require constant fixes. When we rescue failed development projects, it's often because someone prioritized trendy approaches over reliability.
The Genzeon project is instructive here. After two development firms couldn't deliver using modern block-based approaches, we completed the project in 7-8 weeks using ACF and Classic Editor—delivering all the complex design features they needed while creating a content management system their team could actually use independently.
Our Classic Editor + ACF approach aligns with what mission-driven organizations actually need:
Reliability: Sites that work the same way today as they will three years from now
Performance: Fast load times that serve every visitor, including mobile users on slower connections
Maintainability: Clear, documented code that any qualified WordPress developer can work with
Cost-effectiveness: Less time fixing things means lower ongoing costs
Accessibility: Clean semantic markup makes meeting WCAG standards straightforward
Security: Fewer dependencies mean fewer potential vulnerabilities
The Classic Editor Plugin Isn't Going Anywhere
Some worry that choosing Classic Editor means betting on deprecated technology. That's not accurate.
The Classic Editor plugin has over 5 million active installations. WordPress has committed to supporting it as long as necessary. And even if it eventually stops receiving updates, it's a simple plugin—there's minimal complexity to maintain.
More importantly, our custom themes don't depend on the Classic Editor plugin to function. They depend on custom fields (via ACF) and custom templates (core WordPress functionality that isn't changing). The Classic Editor simply provides the content editing interface.
If WordPress ever truly discontinued Classic Editor support, switching to Gutenberg for content editing wouldn't require rebuilding the entire custom theme. The architecture remains sound.
This Is About Building the Right Solution
After two decades of WordPress development, we've learned that the "best" tool isn't determined by which is newest or most popular—it's determined by which delivers the best results for the specific project.
For custom WordPress theme development serving mission-driven organizations that need performance, reliability, and maintainability, Classic Editor + ACF consistently outperforms block-based approaches.
That's not opinion. It's what we've proven across dozens of projects, some running successfully for over a decade.
When you choose FatLab for custom WordPress development, you're working with developers who prioritize results over trends—who build solutions that work reliably for years, not just at launch.
Because ultimately, great WordPress development isn't about which editor you use. It's about understanding your needs, building the right architecture, and delivering a website that serves your mission every single day.
Ready to discuss a custom WordPress project built on stable, high-performance foundations? Learn more about our custom WordPress development services or contact us to start the conversation.