WordPress Alternatives

Original Article ↗ Hacker News Discussion ↗

WordPress’ dominance as an easy, non‑technical way to build websites leaves many developers frustrated but still reliant on it, because few rivals match its “drop it on a cheap host and go” convenience plus huge plugin ecosystem. Commenters highlight alternatives ranging from developer‑oriented CMSs like ProcessWire, Kirby, Drupal and Wagtail to static site generators (Hugo, Jekyll, Astro) and GUI tools like Publii, noting these often trade simplicity and extensibility for steeper setup or weaker theme/plugin markets. Overall, the landscape is rich in technically superior or more focused tools, but there is still no clear, widely accessible, self‑hosted replacement that serves non‑technical users as comprehensively as WordPress.

PHP CMS alternatives (ProcessWire, Kirby, ClassicPress, etc.)

  • ProcessWire is heavily praised: fun to develop with, flexible, suitable for both simple sites and web apps, and easy to update by replacing a single directory.
  • Critiques: less “batteries-included” than WordPress; better suited to developers than non-technical users and has weaker “site profile”/theme marketplaces.
  • Kirby gets positive mentions from long-time users, but some criticize its outdated admin stack (Vue 2).
  • ClassicPress appears as a more “classic” WordPress fork with performance comparisons linked.
  • Other PHP options noted: Textpattern, Dotclear, GetGrav, PluXml, Chyrp Lite, Typecho, Movable Type, BloKi.

Static Site Generators & Static Hosting

  • Many advocate SSGs (Hugo, Jekyll, Astro, Lektor, Middleman, Publii, Quartz, Logseq, Soupault, Pandoc).
  • Pros: security (hard to hack), cheap or free static hosting (GitHub Pages, Netlify, Deno Deploy), version control workflows, performance.
  • Cons: most are poor fits for non-technical users; collaboration and image handling are recurring pain points; commenting is seen as inferior to WordPress’s built-in system.
  • Publii is highlighted as a GUI middle-ground SSG, though collaboration and Git integration are viewed as weak.

Drupal, Wagtail, and heavier frameworks

  • Drupal supporters argue it’s a powerful, extensible, PHP-based alternative with modern initiatives (browser-based “Drupal CMS”, AI tools, commerce/CRM, no-code ECA).
  • Others say Drupal has grown more complex and less friendly for “ordinary” deployments, with many sites stuck on Drupal 7.
  • Wagtail (Django-based) is praised for UX, flexibility, and stability but criticized for opacity, learning curve, and need for substantial developer setup. Some see it more as a CMS framework than a drop-in WordPress replacement.

Hosted platforms, headless, and niche tools

  • Hosted platforms like Wix, Squarespace, Shopify, Ghost (hosted), Hashnode, Bear, Framer, and Sanity (headless) are mentioned as realistic options for non-technical users.
  • Specialized or visual tools: Frappe Builder, Netlify + JAMstack, Astro as a flexible “engine,” magecdn for static image handling.

What people want in a “true” WordPress alternative

  • Desired traits: self-hosted, open-source, easy install, long-lived, rich plugin/theme ecosystem, ACF-like custom fields, Gutenberg-style visual editing, REST API, and workable e-commerce.
  • Many argue that for the vast majority of non-technical users, nothing matches WordPress’s combination of simplicity, ubiquity, plugins, and support—alternatives either lack features or require more technical skill.

Ecosystem & politics

  • Some criticize WordPress’s current ecosystem (naggy freemium plugins, hosting pain, leadership drama), yet others note GPL and forking as safeguards.
  • Political stances by CMS creators (on social media or endorsements) spark debate: some want politics kept out of recommendations, others see ethical stances as necessary.