Thanks for the reply @Paul_Brats . It’s clear the team is putting a ton of work into making Strapi better, and that’s truly appreciated.
Just to share where I’m coming from, I use Strapi more as a straightforward API tool rather than a full CMS. I’ve always seen it as an all-in-one backend solution like what you’d get with ExpressJS. Because of that, the frequent big changes and new features haven’t really benefited my projects, especially since I don’t use many of the CMS features like Draft and Publish or the I18n stuff.
I’m wondering if something like NestJS or Fastify might be a better fit for me.
With that said, I still believe that you are introducing too many breaking changes:
- all of the Strapi blog posts will be outdated (I still regularly land on V3 articles that are useless)
- The Strapi Marketplace will take a massive hit (my prediction is that V5 will never reach the number of plugins that V4 has)
Contrast this with Wordpress, where I managed to upgrade a website made in 2005 in about 10 minutes, without needing to change a single line of code.
I hope you consider the significant impact of these breaking changes, and I wish the best for V5.
Thanks for all your work 