Create a richer cross-platform user experience with headless CMS
- Posted on January 31, 2018
When it comes to offering a powerful digital customer experience, Sitecore delivers. The platform evolves to fit customer expectations and new technologies.
For example, countless clients require access to Sitecore content in the form of a RESTful service. This puts Sitecore at the center of the digital ecosystem, supplying content to many other systems such as single page applications based on Angular and/or React as well as native mobile applications.
Types of CMS
A coupled CMS is responsible for content management and content delivery. It consists of three parts: a database that stores the content, a web application/ content management that provides an interface to manage content and design, and content delivery that generates the HTML experienced by the visitor.
A headless, or decoupled CMS, occurs where the front-end, or “head”, is detached from the back-end that creates and manages content. The back-end delivers the content as a service to the front-end for the content consumer, or customer.
When to use headless CMS
Some advantages of headless CMS include:
- Flexibility: developers can use any front-end customer-facing technology as long as it consumes a RESTful service
- Efficiency: reduced time for creating applications
- Optimization: overall performance improvements by enhancing back-end (API) and front-end implementations
However, it has a few disadvantages:
- Complexity: it becomes increasingly complex to implement each API across multiple systems
- Testing: content authors can’t preview changes on the fly
- Current limitations: marketers will not be able to manage customer experience, will not be able to get contextual insight and personalize the content according to the insights.
- Complications: headless is an overcomplicated solution when building a simple site
How Sitecore supports headless
Sitecore originated as a headless CMS. It stores content as items, and Sitecore’s layout engine places those objects, or modules, in a web presentation format. Similarly, a mobile app developer can use Sitecore API to call those content objects and reuse them in a mobile app. When a marketer changes your brand’s web content in Sitecore, those changes automatically propagate across any channel on which you’ve called or reused those content objects. With Experience Editor, you can edit and preview content components (or modules) on a page. The same actions can be achieved through other products. However, while many other content management systems make it appear as though you’re editing content components on the page, the similarities end there.
JSS will give front-end developers flexibility to build sites using any tools without the restrictions of back-end structures and conventions. It will also allow marketers to get insights context, leverage personalization, and optimize user experiences.
For example, we’d use Content Service to access content items outside of the Layout Service ?itemPath=/homePage where it will resolve the item in a similar fashion as Layout Service does, and returns a serialized version of the item:
"Component Name": "Welcome"
"Title": "Hello from home page"
Powered by Sitecore 9, headless CMS will drive digital marketing far beyond the web. Now you can create web apps, mobile apps, and single page apps using Sitecore JSS to expand your market and reach different user segments.
Here at Avanade, we transfer the potential of headless CMS into tangible results for our clients. Connect with us to determine the right digital content management strategy that will keep you ahead of customer expectations.