I’ve been trying to use Strapi for the past few days and from what I’ve been through, its been a terrible experience.
First off, when trying to get started, one would use a blog/guide right? Well that’s what I’ve decided to use too, and that is where the other side of this “leading open-source headless CMS” started to show. Here is a link to the blog that I’ve decided to use since I am familiar with Next.js. First off, keep in mind that in big letters it says “This article was updated to Strapi v4.”. “Good” - I though to myself, this is the version of Strapi I’m using, so everything should work nicely. Oh boy was I wrong, if you scroll down just a bit to the “Creating a new Strapi application” section, the first thing you see in the docker-compose.yml
is version: '3'
. “Oh no, why would that be?” - I said, since It was my first time using docker and I had no experience with it. Okay, maybe its just the docker-compose.yml
version number? No, it’s litteraly the version 3 of Strapi, and as I found out later, there isn’t even a docker image for Strapi V4. I am not going to talk about the article writer using NextAuth v3 when the latest version is v4, because I think you get my point by now.
Secondly, and maybe the worst thing about Strapi is the documentation.
For 3 days (3!!!), I have been trying to extend the functionality of the users-permissions
plugin by adding a new route and a custom controller. Now, it is a common thing to change user data after the user account was created, and that’s exactly what I’ve been trying to do. If you look at the documentation there is nothing about creating custom controllers for a core plugin (you can see how to create a new route in the Plugins extension section of the docs). I think by now you understand is an absolute mess, and I don’t understand how Strapi could be used by Nasa or IBM, as stated on the homepage.
I am not trying to be rude or ungrateful to the Strapi team, but just trying to shed some light on the caveats for new users wanting to create a project with Strapi.