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.
Mahdi Jabinpour
Building WordPress plugins and AI tools at LumoWP. Practical notes on WooCommerce, performance and multilingual websites.
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.