Honestly this is by far the easiest solution for jumping into the headless CMS world and even better as an API framework to power whatever your needs are; Web, Mobile, Desktop, IOT, and even a smart toaster! The Strapi team is great and works hard to release feature and fix bugs as fast as they can.

Strapi is extremely easy to setup Simple database configuration with many choices (Mongo, Postgres, and MySQL) Simple to modify the backend code Getting up and running from zero to a complete API with data in as little as 10 to 20 minutes

I do think that more time needs to be spent on building a solid foundation (which the Strapi team are working on) More time needs to be spent testing bugs for all usecases (or some automation for the frontend testing needs to be implemented and I believe that is being done right now) While not an issue with the software itself, I do think that services like Heroku need to be put on the backburner and not pushed as heavily as Strapi is a service, Heroku and other "serverless" environments are not built to handle complex applications. At the same time more user involvment with Pull Requests are something that would greatly help development and bug fixing.

Generally Strapi is a great tool with the aim to be a robust CMS for large projects. I have use it to build/manage site which include live streaming, media portals and ecommerce. The "managing" part is fine, but most of the advanced functionality has to be coded additionally.

Strapi - as the name suggest - is an API builder tool which helps you to manage data that is being consumed by frontends and other apps. This functionality is done very well. Strapi provides hooks and cycles to modify data coming in and out of it. But these need to be programmatically configured. Good thing is the Strapi authentification layer and CDN for images.

As Strapi does not provide you with a Frontend it is hard to get the initial concept and add functionality. Every change in the Admin triggers a restart of Strapi and basically means downtime. Sometimes the database gets vacuumed while you try to work with endpoints. This can very frustrating. Same as the responses from Strapi which include nested objects and those are hard to orientate in while consuming the data.

While I was very positive about trying Strapi the Docker image problem soured it and I found alternatives that worked better.

Open source, we can host it ourselves, active community, lots of features and extensions.

The Docker image is one major version behind but this is not made clear until you've spent hours trying to get it all working and then check the forums.

Automatic creation of API endpoints based on content types, Role Based Access Control, Authentication, Querying and Media Library features reduces the time of app development.

Some parts of the Strapi documentation are not clear. It may be necessary to search the forum and the internet for things that can be easily explained with an additional sentence in the documentation.

I have been using Strapi for 3 years and it is a product that I am trying to push to others everytime they need a solution. I mainly use Strapi for frontend site and I rarely use it as an API to an app. But for content management, Strapi beats products like Contentful and Sanity in my eyes because it is open source and you can host it anywhere you want.

To be able to create an API for landing pages in a matter of hours. I created many types of section for my landing and I could start integrating my frontend the next day. My site grew ever since and Strapi made it super easy to add more sections and evolve with time.

One of the main thing I don't like about Strapi is the fact that it doesn't have a good way to be updated easily. I am using a deployment system and I wish I could update it from the admin panel itself. I need to use the command line and to redeploy everytime there is an update. Updating something frequently should not be something negative, but it is with Strapi because I am always in need to keep it up to date. The only other thing, is the lack of Responsive on the admin panel.