Thank you for reaching out and for explaining your concerns so clearly. They are completely valid.
V3 was discontinued primarily due to technical limitations and accumulated legacy code that made long-term maintenance increasingly difficult, especially with newer PHP versions and evolving WordPress core changes. Continuing active development on V3 while also moving the product forward would significantly slow down progress and increase the risk of instability across both versions.
That said, we fully understand the situation of sites that are still running on V3 and are not using Gutenberg. Many existing projects fall into this category, and we agree that a full rebuild is not always a reasonable or realistic option.
Regarding V4 and the editor: V4 does not require Gutenberg. You can continue using the Classic Editor normally, as V4 fully supports shortcodes for all core functionality. This allows existing sites to migrate without being forced into block-based editing or restructuring their content workflow.
In other words, switching to V4 does not mean you must rebuild your site or adopt Gutenberg if you don’t want to. The shortcodes are there specifically to support classic-editor-based sites and legacy setups.
As for V3, while active feature development has ended, we are still evaluating options for essential maintenance updates where feasible, particularly in relation to critical technical issues such as PHP compatibility. We cannot promise long-term support, but we do understand the importance of stability for production sites.
Thank you again for your feedback and for taking the time to share your perspective. We genuinely appreciate it.