7 guides on headless wordpress
Using WordPress as a content backend for React and Next.js frontends — REST API, WPGraphQL, previews, deployment and when headless is worth the extra work.
A practical comparison of headless WordPress (REST API + React/Next.js) and a traditional WordPress theme — cost, speed, SEO, editing and when each one fits.
Read articleGoing headless removes everything your SEO plugin was doing on the front end. Here is the full list of what the frontend now has to render itself.
Read articleTwo applications, two hosts and two deploy pipelines. How to arrange them, keep the CMS off the public domain, and handle builds that need WordPress up.
Read articleTwo features a WordPress theme gave you free that a headless frontend has to rebuild — with the spam, deliverability and relevance problems that come with them.
Read articlePreview is the feature editors miss most in a headless build. How the flow works, how to secure it, and what to do about revisions and unsaved changes.
Read articleHow to wire a Next.js frontend to WordPress: rendering strategy, routing, data fetching, revalidation, images and the pieces that are easy to forget.
Read articleHow the two approaches differ in practice for a headless build — over-fetching, round trips, caching, tooling and maintenance — and which suits which project.
Read articleI build custom WordPress websites, WooCommerce stores, REST APIs and headless builds. See my recent projects or my services in Mumbai.
