WordPress Exodus: Why Experts Fear Losing 15 Years of Content to the Fediverse Unknown
Migrating a mature, 15-year-old WordPress site to a fully federated CMS is widely seen as a massive technical hurdle, especially concerning keeping canonical URLs intact.
The core fight pits familiarity against federation. One camp clings to the 'look and feel' of a powerful, customized WP derivative. Conversely, others push for pure Fediverse function and simplicity, regardless of the messy migration details. haverholm specifically dismissed Ghost for its 'half-baked' ActivityPub and worry over LLM reliance, while noting ClassicPress compatibility with WP-activityPub has reportedly broken. The suggested solution, per haverholm, is to 'slash off all the extraneous bloat' from WordPress itself, rather than adopting a wholly new architecture.
The weight of the argument settles on extreme caution. The consensus acknowledges the complexity of the move. The primary fault lines are between preferring a known, customizable platform (like a lean WP fork) versus committing to a bleeding-edge, federated architecture like Hubzilla, whose true compatibility is still unverified.
Key Points
Migrating established WordPress content is technically fraught.
The general consensus holds that preserving canonical URLs across an entire, large WP installation is exceptionally difficult.
Ghost's ActivityPub implementation is suspect.
haverholm explicitly dismissed Ghost, citing its 'half-baked' ActivityPub and its perceived dependency on LLMs, which the group actively avoids.
ClassicPress is tempting but broken.
haverholm noted that while ClassicPress offers architectural familiarity, its compatibility with the crucial WP-activityPub plugin has failed.
Hubzilla offers hope but lacks clarity.
haverholm saw Hubzilla as 'potentially exciting' due to its Fediverse-first, non-AI stance, but admitted migration details for taxonomies vs. channels are unknown.
Overhauling WordPress is seen as an option, not the norm.
haverholm proposed the specific technical path of keeping the core structure but 'slash[ing] off all the extraneous bloat' to create a lean next-gen fork.
Source Discussions (3)
This report was synthesized from the following Lemmy discussions, ranked by community score.