WordPress alternatives grouped by architecture (static, Git-based, flat-file, headless, hosted) and what each one costs you in a migration.
Building VeloCMS.org
Building VeloCMS.org , A fast multilingual CMS for blogs and online stores. I write about headless CMS, Next.js, SEO and moving off WordPress and Shopify.
Markdown supported · ⌘↵ to post
Mahdi Jabinpour
Grouping these by architecture makes the migration cost much easier to see than a feature checklist would. I would add one acceptance test to the plugin-layer inventory: have the actual editor publish and then revise a representative page on the proposed replacement. Include a form, a reusable content block and the SEO fields they normally touch. A migration can preserve the public page while quietly making routine editorial work dependent on a developer.