As a former CMS product manager and leader of an emerging technologies team, we continue to evaluate solutions for our clients across a number of technologies (PHP, .NET, React, Ionic and Angular) and vendors — Acquia, Kentico, Sitecore, WordPress, etc..
In doing this, we focus on many areas – product features, roadmap strategy, market presence, capabilities, mobile support, cloud deployment and integration with components such as marketing and commerce.
Lately, the demand from our clients has shifted far beyond the corporate website and the need for responsive experiences. Hybrid applications, virtual reality, interactive in-store displays and Internet of Things have created an interesting content delivery demand. In the last quarter alone, more than 50% of our development work at Consensus requires delivery to something other than a web browser.
Luckily, great strides are being made in next generation content managed solutions. Led by new, content-first demands – the rise of the “headless” CMS is taking shape. We are implementing “headless” solutions for a number of clients across across a number of technologies – Kentico, WordPress and Drupal. The solutions range from web-based sales applications to tablet solutions.
So what exactly is a “headless CMS” (important note: not “decoupled”)? It is a content management solution that allows a company to manage content and access it via an API across any number of applications. Unlike traditional CMS solutions, a headless CMS provides a solution without the presentation layer (the “head”) that would determine how the content should be displayed. Instead, the presentation can be completely agnostic – website, mobile app, digital assistant, virtual reality, smart watches, etc.— ideal for the multichannel world where content creators are expected to publish frequently and in many mediums..
As we continue to develop in the headless world, we are already realizing a list of benefits from development to delivery. Here are three of the most impactful:
- We can easily iterate and UAT test with the client by pointing them to a browser for layout and application logic – not always having to deliver an .ipa file.
- The separation of the API makes the content available through any channel and on any device.
- We can use any technology or development framework – as you can imagine, the IT requirements of our clients can vary wildly from project to project.
We look forward to the future of headless apps the opportunities it delivers.
Contact us to talk more about our headless CMS development capabilities.