Strapi Reviews: 4.6/5 — Highly Rated

In general, the resources are extremely simple and give a perfect speed in developing and deploying applications.

The way to perform the relationship between tables in the many-to-many format is still not user-friendly.

I'm using it to support a simple backend framework to gather human resource information in just one place, much like a blog framework and adding some tooling features.

It's very easy to setup strapi. Difference user interaces help you to create content types, releations and fields without any need to code. It comes with a REST and GraphQL API out of the tools, which provide a very good developer experience.

The GraphQL endpoint becomes slowly once you are using more content types with many relations, but the core team is working on that. Also dynamic zones could be more intuitive to use.

Strapi helps us to organize content that is clearly structured (Events) aswell as generic pages, which are embedding other content types.

the simple and quickly understandable operability

Nothing noticed so far. But im not working for such a long time with strapi, so i will see whats coming next.

I am trying to recreate a website for a university project to better communicate the clarity to the other students and the professor.

Just the best CMS. It's headless and help to make a secure and easy database and authentification backend system.

I didn't find the way to secure access to media library.

I had a simply and secure authentification system and database system.

Strapi offers a lot out of the box, and most of it can be had with the free community edition. This is great for those looking for something that you can quickly get up and running. For more advanced functionality, you can fairly easily write custom code / plugins for more complex situations.

CMS publishing workflow is still primitive. Currently only supports a draft and publish status. If a conent item was already published, there is no way to test changes out without unpublishing the content item entirely.

We are creating a somewhat simple CMS backend for a marketing website. After the initial effort to create the components and collection types, it makes content creation and updates a lot easier than having content and pages hard coded on the marketing site itself like we were doing previously.

- Support GraphQL. - Highly customizable. - Good documentation. - Update frequently.

- The free plan supports only three roles. - The interface is ok but not as friendly as other CMS I have used.

I have searched for a CMS support GraphQL to connect to my frontend application. I found Strapi to support GraphQL with ease. Besides, the loading speed is fast.

The user interface for Strapi is incredibly modern and intuitive. As a beginner developer, it has made things a lot easier to grasp as I work my way through tutorials, the Strapi Academy and the documentation. Additionally, the support and help I received from Strapi before even getting started was outstanding.

As I expected with moving from WordPress to Strapi, there are some features that are easily available in WP that aren't in Strapi. The community is active though and so usually there are plugins to help with most general cases.

Having a CMS that is detached from any specific frontend makes updating repeating content very easy.

As we plan to transition to the Jamstack, we were directed to use a headless CMS. Strapi looked like a good option, so we looked into getting it all set up. Within minutes, we had something better than we previously had. Our developers were amazed with how quickly we were able to plug our data, and how we could have non-technical employees use it as well for data-entry and manipulation.

So far, not many dislikes. My main dislike is not being able to manipulate the "id" field. I'd like to use a slug for it rather than a incremental number, but in the documentation, it says it is being worked on for Strapi V4.

Besides the "id" problem, not much else. One of the major benefits is definitely allowing non-technical employees to be able to manipulate data and add information without the need of having a developer or engineer doing it for them. It definitely can speed up many bottlenecks in our workflow.

The hability to self host the product and keep the data at bay. Strapi makes it easy to create and use a customized api that meets the needs of the association in terms of managing its websites and applications.

The product is still relatively new, some things are still not fully working and working with internationalization is still quite challenging.

Strapi helps us moving from a slow and monobloc solution to something more agile. We can focus on content management and creation, and less on website maintenance.

I really enjoy how easy Strapi is. You can build complex APIs including relation, automatic slug, field assertions and so on. You can also define multiple roles and give different read / write / update / delete conditions for each of these roles. You can also give more complex permissions with just a click like "a user can update a resource only if he created it".

Roles management for community edition is quite restrictive. It may not be an issue with other editions but I couldn't try it at this time. Anyway, pricing are quite expensive for small companies.

At the time I write these lines, I've only used Strapi for local development. But it really helped me to develop faster. I used to develop my APIs from scratch.

In my case, I started a Open Source project with React and I need a database with CMS so I decided to use Strapi to learn since I had never used it before

Sometimes, when entering pages and performing certain actions, it shows an error card that doesn't make sense, and it could you confuse making you think that you did wrong

Strapi solved my backend databaseCMS system in my project because I'm simulating an online store to practice Remix Run, Next JS and Astro using React as frontend

It's allowed us to get started very quickly in moving from concept to implementation.

We have had to find some ways to work around free tier limitations as we are working as a non-profit.

We're developing a free and open source infrastructure for the development and sharing of teaching material to help build capacity in developing countries.

Strapi framework is simple to use with very good documentation. It's scalable and has a lot of third-party plugins

Lack of MongoDB support and limited plugin support

It is used as a backend for the blog site, with good query support users can only ask for particular data which keeps data size low.

Good balance between pre-developed structure and flexibility for customisation

That the plugin community is a little limited at present

Smaller organisations like ourselves need frameworks like Strapi to rapidly develop solutions to meet the growing digital demand from consumers.

Single post types and dynamic zone with custom components

Very limited plugins and whatever is available is not well documented.

We are building JAM stack based website for our orgnization as a pilot and once sucessful we plan to migrate many other exisiting sites.

East set up and out-of-the-box functionality.

The default UX could be improved. There are more modern components Strapi could be using for lists, component organization, and editing screens.

Provide an easy way to allow content editors and managers to organize our archival data.

It is javascript based, graphql support, and the ability to run it locally.

Too many bugs, the free tier is trash, there is only 3 roles in the free tier, you can't even delete one of them. No typescript version out of the box.

Making API mockup real quick for demo showcase

strapi offer a great interface, user management et role access base. all that is combined with a great API providing all the information we need about the content of our website

the lack of information and guidance in the interface. I have spent 20 min trying to set roles for my user for allowing them to have user management without giving them full access but I could not succeed, I guess is because I have to pay to have more users.

A client asks me to build him a showcase/portfolio website but he also wants to manage the content and article. I had to find a CMS but not a WordPress. Strapi resolves my issue by offering me exactly what I wanted.

It's quite fast to set up a new Strapi instance for a Jamstack project. The frontend can consume the editor's content with the GraphQL API. You can use an S3-based API to consume your assets. It supports multiple languages also! And the UI is quite nice for editors !

Nothing really bad, but it could be nice to have more features like a deploy button to publish your content on demand. However, you can implement such features by customizing it!Also, the Strapi team is working hard to add a lot of new features!

Allow editors to provide structured content in a Jamstack project.

We adopted Strapi a couple of years ago back in the beta phase, The biggest like is the ability to create custom content fairly easily

Upgrade and migrations are very manual and documentation is a little anemic.

We needed a customizable CMS to integrate with an online learning experience

Strapi is a great headless CMS with a lot of great features. I love the clean UI of Strapi. It's also free and open source.

When I was using Strapi, I found some limitations when working with Typescript. Also, Strapi doesn't offer a free tier for their cloud plan. I have to self-host to use Strapi, otherwise, the pricing increases a lot.

The headless CMSs offer a ton of customizability with models and more. I was able to create custom types depending on my use case, which is possible but tougher with WordPress.