Why would you need a headless CMS? IT is looking to address Agility and Flexibility Organisations want to deliver app-like experiences in addition to regular content pages Javascript frameworks like React and Angular have matured Content delivery channels have increased in number and technology has diversified So, IT needs a flexible, decoupled, developer friendly CMS. AEM's Pillars for Headless GraphQL and Content Services power efficient rendering in client applications and robust APIs for content management AEM's Content Fragment Model editor enables you to define content models, relationships and governance via a no-code GUI. Our content fragment editor is an intuitive user interface for creating and managing content. Experience Fragments can be delivered as json objects or plain html while enabling rich personalisation across channels GraphQL Adobe's GraphQL APIs for Content Fragments supports headless use cases where external client applications render experiences using content managed in AEM. GraphQL is a modern content delivery API that enables highly efficient and performant Javascript-based frontend applications. A GraphQL query only returns the content it needs from a single API call. This results in: faster delivery of experiences that use less data Allows for more sophisticated use-cases without increasing complexity Because of GraphQL's intuitive query language, front end engineers love to use it and opens access to a large talent pool to create experiences in Adobe Experience Manager CONTENT FRAGMENTS Adobe Experience Manager (AEM) Content Fragments are created and managed as page-independent assets. They allow you to create channel-neutral content, together with (possibly channel-specific) variations ... Content Fragments are editorial content, primarily text and related images.
Please use this thread to ask the related questions.
Views
Replies
Total Likes