Organizations that create a lot of content to be used across sites or different applications can use a hybrid headless approach with Adobe Experience Manager (AEM) to add flexibility without sacrificing content authoring capabilities.
If you've done anything with a Content Management System in the past few years, you've likely heard the term "Headless." Headless is used to describe the concept of storing the content within one system and consuming that content for display within another system. The "body" is stored in the CMS while the display or "head" is managed in a different system, leaving the CMS as a "Headless CMS."
Going headless can offer several advantages over a traditional CMS setup. A primary advantage is the flexibility afforded when content can be consumed across various channels and disparate display systems. For example, content may be consumed for display on a website on desktop and mobile, while specific content details can be pulled into relevant sections of a mobile application. Headless systems typically allow as much or as little of the content to be consumed at one time as desired.
When utilizing AEM for headless content, you're able to author the content with regular site authoring in addition to serving it to other systems as headless content. Using AEM to author your content will also allow you to structure and layout your content, and your "head" can use that structure and layout information, allowing authors to have greater control over the site's appearance.
Similar to the previous advantage, your content delivery is also decoupled from the CMS technology. This is useful when multiple teams specialize in different technologies. A team consuming the content for a particular purpose does not need to have any knowledge of the underlying system serving the headless content. This can allow for team efficiency and reduced training overhead.
Read Full Blog
Please use this thread to ask the related questions.