---
title: "Comment by Mahdi Jabinpour on \"What are some good alternatives to WordPress?\" | Hashnode"
description: "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 i"
url: "https://hashnode.com/posts/what-are-some-good-alternatives-to-wordpress/6adcb29d6ddc2b2aa5778b37/comment/6add13f4838a42a2d61b8d56"
---

[Discussion](https://hashnode.com/posts/what-are-some-good-alternatives-to-wordpress/6adcb29d6ddc2b2aa5778b37)

Comment [What are some good alternatives to WordPress?](https://hashnode.com/posts/what-are-some-good-alternatives-to-wordpress/6adcb29d6ddc2b2aa5778b37)

[Mahdi Jabinpour](https://hashnode.com/@mahdi-lumowp)

[Oct 24](https://hashnode.com/posts/what-are-some-good-alternatives-to-wordpress/6adcb29d6ddc2b2aa5778b37/comment/6add13f4838a42a2d61b8d56)

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.
