A new beta version of Strapi was just released and this headless CMS is getting more interesting with every release. If you’ve never heard of an headless CMS, it’s a content management system detached from the front-end unlike other CMSs, such as Wordpress or Joomla, where the front and back-office are hosted and built together.
So, when should you opt for a headless CMS?
This is one of the biggest advantages of using a headless CMS. By having the presentation layer (front-end) and the CMS separate you can easily change the front-end framework without needing to make changes to the back-end, even if your product is already live. This will also allow new versions of your product to be released quicker, since you don’t need to upgrade the entire project. By separating content creation from the presentation layer, there’s also no need for content managers to wait for the new version to be released to continue working on the content.
According to Strapi, another big advantage is security because a database is not needed and there’s no data storage point to be attacked. It is also self-hosted and GDPR compliant.