May 30, 2020, 1:28 am
Note: We used commission links in this article and marked them with “*”. If an order is placed via these links, t3n.de receives a commission.
The open source headless CMS Strapi finally reaches the stable release five years after the initial commit. Those who have so far kept their hands off due to lack of market maturity may want to take a closer look at the content management system.
Strapi is an open source content management system based on Node.js. Five years after the initial commit and three years after the company of the same name behind the software was founded, the promising project from France has finally reached version 3.0.0
Headless … what?
A headless CMS differs from traditional, monolithic CMS in that it is decoupled from the front-end component – that is, what users of an app or visitors to a website see. Most headless CMS, including Strapi, are API-based, in others the content is updated via Git. This decoupling means that a headless CMS means that a wide variety of channels – for example, native apps, IoT device channels or that Web – can be recorded. The platform-based interaction with a wide variety of technologies is one of the reasons why headless CMS are becoming increasingly popular.
That is behind it
Strapi offers a flexible data structure, through which you can define different field types for your content, the possibility of access authentication to API endpoints via JSON web tokens, webhooks and a feature called Dynamic Zones, which enables reusable dynamic entries with complex data structures to build. The content management interface comes with a markdown editor, customizable layout, various filter options and a media library in which different media formats can be saved and edited. Strapi-based projects can be expanded with various plugins to include email, upload and search providers or community plugins for sitemap and import.
While the project had a large user base and a lively community even before the stable release, the blog post for the release announces that the CMS is now officially ready for large-scale enterprise adoption. Overall, the core team for the stable release focused primarily on eliminating pain points and improving the developer experience. The Community Edition offers support for the initial implementation as well as more plugins, integrations and options for costumizing the Strapi environment. The latest version now includes native support for .env files and so-called overwrites to simplify configuration for developers. There are also improved data back lifecycles that allow you to trigger functions before or after a specific event, or to execute a new command line command to make it easier to migrate settings between environments. You can read all the innovations in detail in the associated changelog.
If you want to try out the stable version of the CMS, you can do this using the command
yarn create strapi-app my-project --quickstart do instructions on how to migrate existing strapi apps to the stable release version can be found in the document.
New payment models
Strapi is also launching its first paid model with the stable release. An Enterprise Edition with extensive support is already being planned, interested companies can register for the private beta until July 1st.
Suitable for this: Content for everyone: What is a headless CMS?