Chapter 8

Away from WordPress, and back again

The move rarely fails on the technology. It fails on the question of who maintains the site in six months.

• A single page needs no CMS. Granted.
• The question is not what builds faster, but who keeps it afterwards.
• The client wants to change the opening hours: a text file? Git? A branch? A prompt?
• The compromise everyone lands on in 2026: WordPress behind, Astro in front.
• What gets kept is the back end — the part everyone calls old-fashioned.
• And you need not choose: headless, or shipped from a Git repo through Vercel.

You are not throwing WordPress away. You are throwing the front end away.