Before Astro templates enter the picture, the custom post type should be treated as an API contract inside WordPress. A type that looks fine in wp-admin can still fail headlessly if show_in_rest, public, or publicly_queryable are misaligned. That same discipline…
Astro can mirror WordPress paths in static, SSR, or hybrid mode, but the long-term maintenance cost is very different. Static builds Static output is safest when URLs change rarely and content updates can wait for a rebuild. Every known route…
WordPress content does not arrive in Astro as a finished page. It moves through a pipeline: blocks are stored in the database, turned into HTML by WordPress, sent over an API, then inserted into an Astro template and finally styled…
What is actually being rejected “Without raw HTML hacks” does not mean Gutenberg content contains no HTML. It means a headless build does not treat the post_content string as a frontend API, scrape CSS hooks from saved markup, or patch…
Before any field list is drafted, the model needs its business objects. These are the things that would still exist if WordPress disappeared tomorrow: a product, event, person, location, episode, policy, or campaign. Fields come later. An easy test is…
Astro rendering works best as a three-part pipeline: That separation matters because a raw WordPress post is a poor view model. It usually contains mixed concerns: REST metadata, embedded relations, rendered HTML, dates in multiple formats, and optional fields that…
Static pays off fastest when the site is mostly published content: marketing pages, docs, editorial archives, landing pages, and low-change catalogs. In those cases, the argument in the content-site value case usually holds: fewer moving parts at request time, stronger…
Before any Astro page template exists, the content API has already dictated URL discovery, field shapes, pagination logic, and failure modes during astro build. Changing it later usually means rewriting loaders, not just swapping endpoints. REST is the easier first…
Plugins that print markup into the theme layer are usually the first obvious failures in a headless build. In classic WordPress, a plugin can hook into the_content, inject schema, output a form, append related posts, or render breadcrumbs, and the…
“Headless” describes an architecture, not a different CMS. WordPress does not disappear; its headthe theme layer that turns database content into HTML pagesis removed or bypassed. In its place, another application, often built with React, Next.js, or a mobile framework,…
