Choose what remains in WordPress
Astro can use WordPress as a content source, or the project can migrate content to another system. Keeping WordPress may fit an established editing workflow. Moving away may fit a simpler publication. Inventory plugin responsibilities, custom fields, users, forms and commerce before deciding.
Preview is part of the architecture
Agree how a draft is reviewed, how publication triggers a rebuild and how time-sensitive pages stay current. A fast frontend is not enough if editors cannot see their changes. Test rich text, image captions, embeds and internal links with real content before migrating the archive.
Protect the existing routes
Map posts, pages, categories, author archives and media URLs to explicit outcomes. Keep pages that still serve a purpose, redirect changed locations to an equivalent destination and document retirements. Compare the deployed site with the inventory rather than checking only the homepage.
Sources & further reading
Sources behind this guide, with further detail from the original publishers.
How we publish these guides →