In practice
Strapi works where different groups of users should see different data and a non-technical person manages the content. On Kuma.de I used it for a karate school: custom roles and permissions, data in PostgreSQL, and the school runs its own content. When the CMS should live in the site code, I pick something else.
What is Strapi?
Strapi is an open-source headless CMS that you run yourself or in the cloud, with an admin panel and a plugin system. You create content types in the panel, in the Content-type Builder, and Strapi exposes REST endpoints for each of them by default. GraphQL comes from a separate plugin.
Data goes to SQLite, MySQL, MariaDB or PostgreSQL, and MongoDB is not supported. The panel has a built-in user and role system. Some features, audit logs for example, belong to the paid Enterprise plan.
- Modelling
- Content-type Builder, development environment only
- API
- REST out of the box, GraphQL via a plugin
- Databases
- PostgreSQL, MySQL, MariaDB, SQLite
- Permissions
- Roles and permissions in the panel
How I work with Strapi
I start with people, not fields. I settle who logs in to the panel, what they see and what they can change, because the rest of the model follows from it. Only then do I draw the content types and the relations between them, so the panel shows each group just what it uses.
Roles and permissions
I lay out the roles first and the content types after. On Kuma.de Strapi got custom roles and permissions, and parents have a separate panel showing their child progress.
Model and API
I model content types locally, because the Content-type Builder works only in the development environment, so a model change in production always needs a deployment. The frontend fetches through GraphQL, so each screen takes only what it needs, as on Kuma.de.
Database and deployment
Data sits in PostgreSQL, and the school business logic runs on the server in Node.js. I package it all in Docker, so deployments are repeatable.
When it fits, and when it doesn't
Strapi fits a project where the panel is a working tool, not an add-on to a website.
A good fit when
- A system with accounts and roles, for a school, a club or a small office.
- A team that wants to model content in the panel on its own machine.
- A frontend that prefers to fetch exactly the fields it needs through GraphQL.
- A project on MySQL or MariaDB that you do not plan to change.
Not a fit when
- A project where the data model should live in the same app as the site.
- Editors who are meant to add new content types in production.
- Data already sitting in MongoDB that should stay where it is.
- A team that will not use a paid plan but needs audit logs, say.
When the CMS should run with Next.js in one repository, the side-by-side with Payload CMS is in that entry. For a simple editorial site I look at WordPress as well.
Frequently asked questions
Looking for a CMS for a system with roles?
Describe which groups should see which data and what you use today. From that I will judge whether Strapi is enough or whether the project belongs on another tool.