Developer migrated a 19-year-old WordPress blog to a custom markdown-first static site (Yapress) after hosting pain and archive control frustrations.
Key Takeaways
Trigger was a Bluehost migration gone wrong: unreliable response times, buggy Cloudflare integration, and support that couldn’t diagnose root causes.
Core problem was WordPress’s archive usability: no local search, no Git versioning, no easy reorganization of years of posts across topics and languages.
Built Yapress (initials + press) using Codex, Claude, and Gemini; supports WordPress import, taxonomies, series, content validation, and a static plugin system.
Trade-offs accepted: dropped native comments, built a custom subscription plugin, chose Next.js for familiarity over Cloudflare free-tier optimization.
Key framing: AI dropped the cost of replacement low enough that the question shifted from “can I afford to change?” to “can I justify not changing?”
Hacker News Comment Review
WordPress’s storage format is the deeper structural issue: posts stored as hybrid HTML/JSON-in-comments blocks, plugin metadata as serialized PHP in separate tables, creating compounding technical debt.
Commenters flagged that Kirby CMS already solves the flat-file, markdown-first pattern with more polish than a vibe-coded custom tool.
Notable Comments
@chuckadams: “WP’s” storage is “a wobbly Jenga tower of technical debt” – shortcodes, block JSON in HTML comments, serialized PHP metadata all layered together.
@addedlovely: Suggests Kirby CMS as a prior art alternative with more refinement than a from-scratch vibe-coded setup.
