Jean Galea

AI, Investing, Health, and Building Businesses

  • Start Here
  • AI & Tech
    • AI
    • Tech
    • Modern Web Stack
    • Business
  • Investing
    • Investing Basics
    • Crypto
    • Stocks
    • P2P Lending
    • Real Estate
    • Calculators
    • Dividends
    • FIRE & Early Retirement
    • European Investing Hub
  • Life
    • Essays
    • Barcelona
    • Padel
    • Health & Fitness
    • Hobbies
    • Family
  • About
    • My Story
    • Projects
    • AI Consultancy
    • Plugins
    • Speaking
  • Blog
  • Community
    • Good Life Collective
    • Daily Driver AI
  • Search

Headless WordPress: The Bridge

Last updated: October 31, 2026Leave a Comment

The Faust.js homepage, a headless toolkit for WordPress built on Next.js

This is part of a series on the modern web stack, written from a WordPress developer’s seat for people who’ve built on the web for years and still hit stack terms they can’t define. The goal is literacy, enough that you can read any stack list and know what each piece does.

Each post has a 10-15 minute audio companion, generated with NotebookLM, for the gym or the commute.

Headless WordPress has been pitched at most WordPress veterans three times in five years. In 2019 it was decoupled themes as the future. In 2021 it was Next.js and Faust.js. In 2024 the agencies said it had matured. Each time the pitch called headless the inevitable next step for the platform, and most developers shrugged and went back to building Genesis child themes.

The skepticism was earned. Headless adds complexity, and it adds real value for specific project shapes. Telling the two apart, without dismissing the idea or swallowing the marketing, is one of the more useful things a WordPress developer can carry into 2026.

This post covers what headless WordPress is, when it pays off, when it doesn’t, and where WordPress sits as a backend in the stack the previous posts walked through.

What Headless Means

Headless means using WordPress as the content management system while rendering the frontend with something other than its PHP templates. The backend keeps doing what it’s good at: editorial workflows, roles, the block editor, custom fields, the plugin ecosystem. The frontend becomes a separate application, built with Next.js, Astro, Nuxt or a static site generator, that fetches data from WordPress over an API.

There are three pieces.

The content source

A regular WordPress install, with the admin at cms.example.com or example.com/wp-admin. Editors use the block editor as usual, and posts, pages, custom post types and custom fields all work.

The API

WordPress exposes its content through the REST API (/wp-json/wp/v2/posts) or through GraphQL with the WPGraphQL plugin. Either way the frontend consumes JSON.

The frontend

A separate application that fetches from the API, renders pages with React, Vue or Astro, and serves them to visitors. It can sit on Vercel, Cloudflare Pages, Netlify or anywhere else, and it runs independently of the WordPress install. The earlier posts on Next.js and hosting beyond Kinsta cover this side in more detail.

The trade-offs:

  • A faster frontend, since there’s no PHP rendering on every request.
  • A better developer experience: a modern JS toolchain, type safety, component reuse.
  • More moving parts: two codebases, two deploys, content invalidation to manage.
  • No WYSIWYG preview in the WordPress admin unless you wire up a preview integration.

The decision comes down to whether the development and frontend gains are worth the operational complexity. An editorial team that publishes several times a day, with a frontend that needs more interactivity than a theme gives, increasingly says yes. A small business site that updates twice a year still says no. The post on when not to use Next.js applies here too.

The WordPress Analogue

Headless WordPress is a restaurant with a separate kitchen and dining room, where a traditional site runs both from the same counter.

The chef (WordPress) still cooks the content. The dining room (the modern frontend) is designed and operated separately, and the food travels between them on a tray (the API). Once the operation is large enough, both rooms work better for it. For a small operation it’s overhead.

WordPress as a CMS is still excellent. The 2026 block editor is productive, ACF still does what ACF does, and twenty years of work on editorial workflows, roles, scheduled publishing and multi-author bylines is hard to replace. Replacing the frontend is far easier than replacing that.

The Headless Patterns That Work

These are the main patterns in 2026.

WP REST API as data source

WordPress’s built-in REST API returns posts, pages, terms, media and custom post types as plain JSON, with nothing to install. Most modern frontends can consume it directly, and it’s enough for many headless setups.

WPGraphQL

A community plugin, now owned by WP Engine, that exposes WordPress data through GraphQL. It helps when the frontend needs many related entities in one query. It takes more setup and has a steeper learning curve, and gives a better developer experience on complex applications.

Faust.js

Faust.js is a framework for headless WordPress with Next.js, maintained by WP Engine. It handles authentication, preview and routing conventions, which makes it the most batteries-included headless option in 2026. It’s tied closely to WP Engine’s hosting but works without it.

WordPress as CMS for static sites

Author in WordPress, build a static site with Astro, Eleventy or Hugo that fetches content at build time, and serve the HTML from any CDN. WordPress disappears from the public face of the site and lives only behind the admin URL. For content-heavy sites it’s the most performant pattern.

Decoupled islands

A mostly static frontend with small WordPress-powered widgets, such as a search box, a comments section or a member area, embedded through fetch calls. The site reads as static but pulls live content where it’s needed.

Approach Best for Frontend Trade-off
WP REST + Next.js Editorial sites with an interactive frontend Next.js, Astro, Nuxt Most flexible, more wiring
WPGraphQL + Faust.js Larger projects, complex content models Next.js (Faust adds the conventions) Strong DX, WP Engine ecosystem
WP + static site generator Content sites that rarely update Astro, Eleventy, Hugo Best performance, slower content turnaround
Hybrid (decoupled islands) Mostly static with dynamic widgets Any modern framework Most complex, very fast

The default decision tree for 2026: an editorial team with a complex frontend gets WP REST plus Next.js, and WPGraphQL only if the content model demands it. A content site without much interactivity gets WordPress plus Astro. A small site that rarely updates stays on traditional WordPress, because headless pays nothing there.

What This Changes for WordPress People

Three practical implications.

You can keep the WordPress admin your clients love. Editorial teams know how to add a post, schedule it, manage media and tag content. Replacing those tools is expensive and politically hard, and headless lets you upgrade the frontend without disrupting them.

The agency offering changes. “We modernize your frontend with Next.js while keeping WordPress as your editorial backbone” lands better with skeptical clients than “we’re rebuilding everything.” Hybrid stacks are easier to scope, easier to roll back and lower risk for everyone.

The WordPress economy also reshapes around the pattern. WP Engine bought WPGraphQL and Faust.js to anchor a headless offering, and Kinsta and Pantheon sell similar bundles. Smaller agencies specializing in WordPress plus Next.js charge more than traditional WP shops because the skill set is rarer. For WordPress developers willing to bridge into modern frontend work, the rate card goes up.

The Rough Edges

A few traps.

Preview

WordPress’s Preview button assumes WordPress renders the page. In a headless setup you have to wire it to your separate frontend. Faust.js handles this for Next.js, and other setups need custom work. Get preview working on day one or your editorial team will revolt.

Cache invalidation

WordPress generates content and the frontend caches it, so when an editor updates a post the frontend has to know. Webhooks, on-demand revalidation and time-based regeneration all work, each with trade-offs. Set it up explicitly rather than by hope.

Plugins

Many WordPress plugins assume they own the frontend. SEO plugins such as Yoast, Rank Math and The SEO Framework need adaptation. Form plugins such as Gravity Forms and WPForms often need a custom frontend, and analytics plugins stop working. Audit what you depend on before committing to headless.

Operations

Two codebases mean two deploys and two on-call rotations. The WordPress install needs its own hosting, security updates and monitoring, and so does the frontend. For a solo developer that’s more work, so budget for it. The later post on how the pieces wire up shows what the frontend half looks like end to end.

WPGraphQL maintenance

WPGraphQL was a one-person project until 2024, when WP Engine took it on. The future looks steadier now, but the schema can still shift between versions. Pin your dependencies.

Go Deeper on Headless

A few resources if you want to build real intuition.

YouTube, gym or commute friendly

  • “Headless WordPress with Next.js” tutorials by WP Engine, in various lengths. They’re sponsored but technically correct.
  • “WordPress as a Headless CMS” by Casey Bisson on the Pantheon channel, about 30 minutes. It takes a vendor-neutral view of the patterns.

Official docs worth bookmarking

  • WP REST API Handbook, the canonical reference. Read the Authentication and Filtering pages first.
  • WPGraphQL docs, the daily reference once you commit to GraphQL on WordPress.
  • Faust.js docs, useful for the patterns even if you don’t use Faust.

The next post is the keystone of the series: how the pieces wire up, with Next.js, Supabase, Drizzle, auth, Vercel and GitHub Actions end to end. Few posts explain it, which is why it comes last.

Related

Docker container engine logo — the container platform that powers tools like wp-env, DDEV, and DevKinsta for WordPress development
Local WP vs Docker: When to Use Each for WordPress Development
wordpress replacement
Is There a WordPress Replacement in 2026? I Went Looking
What’s Beyond WordPress?
My Thoughts on WordPress in 2020
Developer workspace with a colorful code editor on a screen lit by ambient blue and red lighting
The Complete Guide to Local WordPress Development and Testing
When Headless WordPress Is Worth It (and Why Speed Isn’t the Reason)
When Headless WordPress Is Worth It (and Why Speed Isn’t the Reason)

Filed under: Modern Web Stack for WordPress Developers

Part 15 of 16 · Modern Web Stack for WordPress Developers

← PreviousTailwind, shadcn/ui, and the New Design-System MetaNext →How the Pieces Wire Up: A Modern Stack Integration Tour
All 16 modules
  1. Why Modern Web Feels Alien to WordPress Devs
  2. JavaScript and TypeScript for PHP People
  3. React, in WordPress Terms
  4. Next.js: The WordPress of React
  5. When NOT to Use Next.js
  6. Beyond Shared MySQL: Cloud Databases for WordPress Developers
  7. From WPDB to Drizzle, Prisma, and Kysely
  8. Auth in 2026: What Replaced wp_users
  9. Hosting Beyond Kinsta: Vercel, Fly, Railway, Cloudflare, and Friends
  10. Serverless and Edge Functions, Finally Explained
  11. Docker for WordPress Developers
  12. CI/CD: Goodbye FTP, Hello GitHub Actions
  13. Observability When You Can't Just SSH In
  14. Tailwind, shadcn/ui, and the New Design-System Meta
  15. Headless WordPress: The Bridge
  16. How the Pieces Wire Up: A Modern Stack Integration Tour

About Jean Galea

I build things on the internet and write about AI, investing, health, and how to live well. Founder of AgentVania and the Good Life Collective.

Leave a Reply Cancel reply

Thanks for choosing to leave a comment. Please keep in mind that all comments are moderated according to our comment policy, and your email address will NOT be published. Please Do NOT use keywords or links in the name field.

Jean Galea

Founder | AI builder | Dad of three | Athlete

Follow @jeangalea

  • My Padel Journey
  • Affiliate Disclaimer
  • Cookies
  • Contact

Copyright © 2006 - 2026