Between mobile apps, newsletters, product showcases, voice assistants, and connected screens, there's a need for a centralized, flexible, and scalable back office. That's where Strapi comes in. In this article, I explain what Strapi is, how it works, and how it compares to a tool like Prismic, which is well-known in modern web projects.
Strapi is what’s called a "headless" CMS (like Prismic). In other words, it’s a content management system that handles only the content—texts, images, authors, dates, etc.—without dealing with visual presentation.
Unlike WordPress or Joomla, Strapi does not generate HTML pages. Instead, it provides an API (application programming interface) to send this content wherever it’s needed: a website, mobile app, kiosk, and so on.
Strapi is also:
Using Strapi is pretty straightforward, even for non-technical users:
Here’s why more and more teams are choosing Strapi:
For me, Strapi's main added value is the ability to self-host your data (for example, if you have a client who is a government agency and cares about data sovereignty) and also to edit the back office to reflect your client’s brand.
The tradeoff is that development gets a bit more complex, and the interface is a bit less friendly compared to Prismic.
So it’s really the client’s expectations and needs that will determine my choice between these two headless CMS options. I’m a freelance developer specializing in Prismic for several years, but Strapi is also a choice I offer my clients if their needs are a bit more complex.
If you want to learn more about Prismic, I invite you to check out my articles on the subject👇
Comments
Log in to add a comment
Sign in with Google