You might have already heard about Headless CMS and you may be wondering if you should go “all-in” with this new model.
In our complete guide, we are going to answer the most common questions, such as
What is the difference between Headless and traditional CMS?
Is headless the best choice for your next website implementation?
How to use a headless CMS for your next project
It’s best to understand what Headless CMS means before making any decision to start developing your next web project on a content delivery model that won’t fit.
At One Inside, our expertise relies on the implementation of the Adobe CMS, Adobe Experience Manager (AEM). We can show you what AEM can do in regards to content delivery — and in which case headless is recommended.
What is a traditional CMS?
This is likely the one you are familiar with. Traditional CMS uses a “server-side” approach to deliver content to the web.
The main characteristics of a traditional CMS are:
Authors generate content with WYSIWYG editors and use predefined templates.
HTML is rendered on the server
Static HTML is then cached and delivered
The management of the content and the publication and rendering of it are tightly coupled