Hey everyone,
At my company, we're considering making a shift from standard WordPress setups (where we use custom-coded themes and ACF, along with some of our own plugins) to either:
- A headless WordPress setup using React or Next.js for the front end,
- Or adopting PayloadCMS, which is also headless but designed specifically for use with Next.js.
Given that most of our work revolves around marketing—mainly creating landing pages, SEO-focused blogs, and a few e-commerce sites—we're motivated by the desire to branch out beyond just being 'WordPress developers,' as that's where most of us began. Plus, we have a solid background in React from our side projects.
Has anyone here had experience with either approach? What are your thoughts on which one has been more effective? How do you find working with the WP REST API or GraphQL API for headless setups?
5 Answers
If your team is familiar with Next.js, Payload might be the way to go. It allows for more control over your data models and has a better integration with the Next framework. But remember, your clients might have to adjust to a new interface since Payload isn't as familiar as WordPress.
Headless WordPress can be convenient since it keeps your existing plugins and workflow, but it definitely comes with challenges, especially when maintaining two codebases. If you're looking for long-term growth and flexibility, consider that going with Payload might be more beneficial, even if it requires some migration effort.
I've migrated several clients from WordPress to Payload and the feedback has been outstanding. Clients enjoy the custom admin interfaces, and I find it easy to build cool features with Payload. Plus, it automatically generates TypeScript interfaces for your models, which is a nice perk.
If most of your work is in marketing or landing pages, I’d lean towards PayloadCMS. It’s all built on Next.js, so your team can focus on one tech stack instead of juggling WordPress. While headless WordPress has its perks, you still have to deal with updates and security for the WordPress backend, which can add extra complexity.
I've worked with both setups, and honestly, Payload offers a much smoother developer experience right off the bat. The way it handles custom fields and post types is similar to ACF but without the WordPress overhead. If you're mostly reliant on ACF for data management, Payload might save you a headache in the long run.
Related Questions
How to Build a Custom GPT Journalist That Posts Directly to WordPress
Cloudflare Origin SSL Certificate Setup Guide
How To Effectively Monetize A Site With Ads