Perfect use for Strapi here, we cover all those bases
Doable but this would be handled in your “Frontend” making the API requests to Strapi (certain aspects may require some custom controllers but it’s fairly straight forward on building).
I would say this isn’t really a Strapi thing, your frontend (nuxt/next) would be generating the SEO from content within Strapi
- You can get a prototype up in running in minutes for the Strapi backend part, there won’t really be a net gain/loss with custom on the next/nuxt side as you are still speaking to a backend that you have to write logic for in the frontend.
- Strapi can look a little complex, but I’m not sure exactly what you mean here. Simplicity in what context? Maintainability is also largely subjective.
- I would say our focus on trying to be as low-code/no-code as possible would certain count as a gentle learning curve. If you are even remotely familiar with Koa.js (made by the same devs as Express) then it’s pretty easy to catch on.
- We have tons of learning resources, and well you are here getting support
I won’t give my pro/con list as I feel this is certainly subjective to the use case, and well I’m bias considering I work for Strapi so I’ll let others answer in my place there 