Breaking Up with WordPress After Two Decades
After two decades of using WordPress, the author decided to migrate their personal website due to frustrations with hosting reliability and the limitations of WordPress for managing an extensive archive of writing. They created a custom markdown-first static site solution called Yapress to gain better control over content organization, searchability, and versioning. While the transition required significant effort, it provided a more intentional and maintainable way to manage their body of work.
- ▪The author migrated their website from SiteGround to Bluehost for cost reasons, but experienced unreliable uptime and poor support.
- ▪WordPress no longer met the author's needs for organizing and interacting with a large personal archive of writing.
- ▪The author developed Yapress, a markdown-first static site system, to enable local editing, Git versioning, and better content structuring.
- ▪Yapress supports WordPress import, taxonomies, series, and URL preservation to maintain legacy links.
- ▪The new system trades dynamic features for simplicity, control, and long-term maintainability.
Opening excerpt (first ~120 words) tap to expand
PostSpaciousEditorialBreaking Up With WordPress After Two DecadesPublished April 15, 2026 · 6 min readAround Black Friday last November, I moved my website from SiteGround to Bluehost. This was not some ambitious infrastructure decision. SiteGround wanted roughly five times more at renewal, and both providers are shared hosting anyway. Bluehost was materially cheaper and advertised 99.9% uptime, which seemed good enough on paper. For a personal website, forty-three minutes of downtime a month did not sound like a serious trade-off. I do not need elite infrastructure for a blog. But I also do not want emails from updown.io telling me the site is down, or someone complaining that it broke halfway through reading. So I did the migration. Boy, was it painful.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Hacker News: Front Page.
Discussion
0 commentsMore from Hacker News: Front Page
