Notes from compiling the future of publishing.

Searching for a fast, self-hosted, open-source WordPress alternative in 2026? We compare Neopress (native Rust + SQLite CMS with 1-click Elementor/Divi/Gutenberg migration and built-in MCP server) against Ghost, Strapi, Payload CMS, and Hugo.

Why does every developer tool website look like a dark-mode purple SaaS dashboard? For Neopress, we went back to 1960s Swiss broadsheets, warm newsprint, woodblock plates, and an honest ledger of what works and what doesn't.

WordPress's wpautop, sanitize_title, and shortcode_atts have twenty years of quirky edge cases. Guessing how they behave breaks URLs and layouts. Here is how our Golden Master verification loop guarantees byte-for-byte parity.

When AI coding assistants edit a CMS today, they usually dump brittle raw HTML blobs into a text field. With Neopress's built-in /mcp endpoint, agents read and write native NeoStudio AST trees and ElementorKit design tokens.

The hardest part of leaving WordPress isn't moving wp_posts rows—it's rescuing pages trapped inside Elementor _elementor_data JSON, nested Divi shortcodes, and Gutenberg block comments.

After fifteen years of maintaining WordPress sites, I got tired of babysitting PHP-FPM workers, Redis caches, and 40-plugin stacks just to serve mostly-static HTML. Here is why we are compiling the CMS into a single Rust + SQLite binary.