Jeroen Fürst shares his thoughts on how headless CMS boosts productivity and helps you save time with creating content that can be shared across multiple channels.
Radka UhlirovaJun 13, 2017
Jeroen Fürst, Lead Developer at TrueLime, presented an interesting case study at the Kentico Roadshow in Amsterdam, where he explained how TrueLime created their company blog website using Kentico Cloud. We asked Jeroen a few questions about the benefits of a headless CMS and which projects he thinks best fit a headless solution.
Learn more about the building of the TrueLime company blog at the end of this blog post in Jeroen's presentation about content-first planning and choosing the right technology.
Which projects are, in your opinion, best suited to a headless CMS?
The best projects for a headless CMS are those that require content distribution across multiple channels. If you, as a company, strive to follow an omnichannel strategy, which you should do to improve customer experience, a headless CMS is your best choice. The majority of our projects require us to copy and share content between corporate websites, intranets, and mobile applications. With a headless CMS, content is automatically shared from a single source. As a result, your productivity increases, allowing you to spend more time on the things that matter—like creating quality content for great customer experiences.
Where do you see the biggest difference between a traditional CMS and a headless CMS?
Content planning, particularly content creation, takes place earlier in the development lifecycle. The biggest benefit of this approach is that we can actually develop our web applications using production content. Because headless CMS is all about the content, it allows us to be creating content and developing the web application at the same time. Also, as content publishing is disconnected from its presentation, the information architecture is simpler than a traditional CMS, where you would have to create content types purely for presentation purposes.
What was the biggest difference in your development and deployment process?
The biggest difference is that we usually spend quite a lot of time installing, hotfixing, and upgrading a traditional CMS during development. A headless CMS, however, does not require this kind of maintenance as it is part of the service (SaaS) and occurs in the background without us even knowing. Hence, we can shorten development time.
How would you explain the benefits of headless CMS to your client?
A headless CMS enables much easier microsite launching for short-term marketing campaigns—keeping design and content requirements to a minimum. Whereas a traditional CMS is often driven by its feature set, a headless CMS focuses on content creation.
What would be your recommendation for other agencies starting with a headless CMS?
I recommend checking the resources from both functional and technical points of view. As for functionality, you'll want to train your content editors quickly so that they can start working on content as soon as possible. As for technicalities, the solution has to fit into the current technological landscape of the company.
With Kentico Cloud headless CMS, you can onboard quickly. You can test the solution for one month and then get feedback from your IT and content teams about their experience. What's more, upgrading from a free to a paid plan is easy and you can keep all the hard work you did during the trial.
We want to thank Jeroen for answering our questions and providing us with his presentation from the Kentico Roadshow, Connecting the Clouds.