Most WordPress plugins do not keep “working” after a static export. The decisive rule is simple: a static site contains only WordPress’s generated output, not the live WordPress runtime that normally executes PHP, queries the database, checks sessions, and runs…
A WordPress export is usually only XML A standard Tools → Export file can look complete because it lists posts, pages, menus, custom fields, and attachment records. Those attachment entries are database content: filenames, captions, GUIDs, and URLs. They are…
Static delivery matters less as a philosophy than as a risk and cost profile. When pages are served as files from an edge network, the request path is shorter and more predictable. That usually produces better Core Web Vitals, especially…
A static WordPress setup has two separate states. Inside WordPress, pressing Publish updates database records: post status, timestamps, revisions, metadata, taxonomy links, and often webhook events. That is the editorial state. The public site follows a different clock. Nothing visible…
In a headless WordPress setup, WordPress stops being the system that renders the public site. It still stores posts, taxonomies, SEO fields, and editorial settings, but another application—often Next.js, Nuxt, or a custom frontend—decides the URLs, page templates, navigation, and…
WordPress normally builds each page at request time. PHP runs, the database is queried, plugins modify output, cookies identify the visitor, and the final HTML is assembled on the server. A static site changes that model completely. Pages are generated…
Astro’s default model assumes content is known at build time. A page is generated from a stable URL, using a query that returns only publicly visible records, and that HTML is then frozen until the next build. That works perfectly…
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…
