Evolve18 | Abhishek Dwevidi & Varun Mitra | AEM as Headless or Hybrid CMS
Download as PPTX, PDF2 likes524 views
AEM can support headless and hybrid content delivery models by providing content services that allow raw content to be accessed via APIs and delivered to various channels. It offers fluid experiences through content and experience fragments that allow for page-independent content creation and reusable layout components. The Experience Editor for SPA also allows for editing content directly within single page applications. AEM's capabilities address reasons why customers want headless solutions, such as omnichannel demands, front-end challenges, and IT challenges around server environments and microservices.
Evolve18 | Abhishek Dwevidi & Varun Mitra | AEM as Headless or Hybrid CMS
- 1. #evolve18 AEM AS HEADLESS OR HYBRID CMS Abhishek Dwevedi 08/17/2018
- 2. #evolve18 2 AEM as Headless or Hybrid CMS 1. Fluid Experiences 2. Why Headless? 3. How AEM Supports Headless? 4. Content Services 5. Single PageApplications
- 3. #evolve18 3
- 4. #evolve18 4 TYPICAL HEADLESS SCENARIOS • Delivery of raw content in native mobile apps • Delivery of raw content to web sites powered by Single Page App (SPA) framework • Deliver raw content to third-party server applications (web, desktop, mobile)
- 5. #evolve18 5 WHY CUSTOMERS WANT HEADLESS Omnichannel Demands • Increasing number of channels / end points, including IoT • Increasing number of technologies to support and maintain Front-end Challenges • Highly customized presentation/delivery needs (M&E industry, for example) • More control over front-end via JavaScript frameworks (Angular JS, React JS, etc.) • Less specialized training and lower learning curve• ITChallenges • Desire to decrease number of servers / environments • Drive towards micro-services architecture
- 6. #evolve18 6
- 7. #evolve18 7 FLUID EXPERIENCES: THE FOUNDATION FOR HYBRID DELIVERY Design, create, curate and use page- independent editorial text content with embedded or associated media. Content Fragments Experience Fragments A group of components with layout that can live independently Content Services A lightweight, read- only way for accessing content (e.g. JSON) from AEM to deliver to any channel
- 8. #evolve18 8
- 9. #evolve18 10 EXPERIENCE EDITOR FORSPA SPA implementation JS Framework Experience Editor forSPA Content Services AEM Server
Editor's Notes
- #5: Content delivered to Point of Sale and other store experiences where AEM doesn’t own the glass Content delivered to offsite digital experiences: affiliates networks, partners, marketplaces, social networks, etc. Connected cars Targeted content fragments delivered to IoT (smart cities, smart homes, fleet updates, etc.) Content delivered to wearables Content delivered to call center agents (Genesys, SugarCRM, SF.com, etc.) Emerging experiences: chatbots (WeChat), gaming platforms (Xbox Mall)
- #11: In-context editing SPA, like server rendered pages, supporting: Insert components Reorder components Edit components Layout components Editor features that might come later for SPA: Component drop targets (eg. for images) In-place text editing In-place image editing Targeting