Permission considerations for headless content. A modern content delivery API is key for efficiency and performance of Javascript-based frontend applications. Learn about the concepts and mechanics of authoring content for your Headless CMS using Content Fragments. Implementing Applications for AEM as a Cloud Service; Using. e. Tap Create new technical account button. Explore the power of a headless CMS with a free, hands-on trial. supports headless CMS scenarios where external client applications render experiences using content managed in AEM. Understand how it can help content authors deliver exceptional experiences, increase their content velocity, and how provides a state-of-the-art. Headless unlocks the full potential of shopping experiences by letting merchants quickly author and deliver app-like experiences across any touchpoint, including single-page and multi-page web apps, mobile apps,. ”. ; Be aware of AEM's headless. They can continue using AEM's robust authoring environment with familiar tools, workflows. Content Fragments used in AEM Headless content modeling, often reference image assets intended for display in the headless experience. On the toolbar, click Download. js (JavaScript) AEM Headless SDK for Java™. They can also reuse content across sites, easily manage metadata and tagging, and accelerate translation to quickly build better digital journeys for your customers. In the last step, you fetch and. SPA Editor Single Page App in React or Angular. 5. Developer. ) that is curated by the. This journey is designed for the developer persona, laying out the requirements, steps, and approach of an AEM Headless project from a developer’s perspective. A Headless Content Management System (CMS) is a back-end only content management system, designed and built explicitly as a content repository that makes content accessible via an API, for display on any device. This provides huge productivity. The diagram above depicts this common deployment pattern. Learn about the different data types that can be used to define a schema. Let’s define what a headless CMS is now. AEM Gem session Search forms made easy with the AEM querybuilder for a detailed overview of the query. This all means that it can be used as a: Headless CMS. In this part of the AEM Headless Developer Journey, learn about headless technology and why you would use it. With Adobe Experience Manager version 6. A “headless” CMS is a content management system that lets you take content from a CMS and deliver it to any front end using any framework of choice. Your CMS is truly headless only if the content is completely separated from the context it is displayed in, that is, you should be able to change the destination of where the content goes, and have your front end determine where and how to layout the content. A headless CMS i s a content management system (CMS) that lets you take content from the CMS and deliver it to any front end using any framework of choice. 2. The session will be split in two halves as follows: Part 1: AEM as a headless CMS Where/When/Why? Presenter: Vengadesh Shanmugavelu - Technical Architect, Qatar Airways. It is a traditional, monolithic CMS with a content-as-a-service (CaaS) API. The AEM Headless Client for JavaScript is used to execute the GraphQL persisted queries that power the app. This article builds on these so you understand how to create your own Content Fragment Models for your AEM headless. The value of Adobe Experience Manager headless. If auth param is a string, it's treated as a Bearer token. After a user creates a Content Fragment based on the Article model, it can then be interrogated through GraphQL. Example applications are a great way to explore the headless capabilities of Adobe Experience Manager (AEM). Examples can be found in the WKND Reference Site. Organize and structure content for your site. For publishing from AEM Sites using Edge Delivery Services, click here. The diagram above depicts this common deployment pattern. The journey will define additional personas with which the content architect must interact for a successful project, but the point-of-view for the journey is that of the content architect. Authorable components in AEM editor. This is the same framework used to translate other AEM content, such as Pages, Experience Fragments, Assets, and Forms. Because of the full-stack development time necessary for AEM Sites up front, Franklin is absolutely going to get your content out the door faster. Get to know how to organize your headless content and how AEM’s translation tools work. Create Content Fragments based on the. This guide provides an overview of Experience Manager as a Cloud service, including an introduction, terminology, architecture, and so on. The Story so Far. Create Content Fragments based on the. An end-to-end tutorial illustrating how to build-out and expose content using AEM and consumed by a native mobile app, in a headless CMS scenario. Adobe Experience Manager as a Cloud Service’s Cross-Origin Resource Sharing (CORS) facilitates non-AEM web properties to make browser-based client-side calls to AEM’s GraphQL APIs, and other AEM Headless resources. granite. It's a back-end-only solution that. In terms of authoring Content Fragments in AEM this means that: For the purposes of this getting started guide, you are creating only one model. Created for: Beginner. Once headless content has been. It separates content from the presentation layer (the head), creating blocks of content that can be delivered in a channel-neutral format to power any channel or experience. The. Implement and use your CMS effectively with the following AEM docs. Be aware of AEM’s headless integration levels. Authoring Basics for Headless with AEM. Headful and Headless in AEM; Headless Experience Management. In this part of the AEM Headless Developer Journey, learn about what is required to get your own project started with AEM Headless. With a headless implementation, there are several areas of security and permissions that should be addressed. In this session we will cover Adobe Experience Manager fluid experiences and its application in managing content and experiences for either headful or headless CMS scenarios. In this part of the AEM Headless Developer Journey, learn about headless technology and why you would use it. Get started with Adobe Experience Manager (AEM) and GraphQL. Authorable components in AEM editor. Clone and run the sample client application. With Headless Adaptive Forms, you can streamline the process of. This exceptional AEM GEMs session features two speakers who are operating AEM as customers. Get to know how to organize your headless content and how AEM’s translation tools work. For ease of authoring content, having easy-to-use. If auth param is an array, expected data is ['user', 'pass'] pair, and Basic Authorization will be used. This tutorial explores how AEM’s GraphQL APIs and headless capabilities can be used to power the experiences surfaced in an external app. The AEM Headless SDK is available for various platforms: AEM Headless SDK for client-side browsers (JavaScript) AEM Headless SDK for server-side/Node. ; The data types Content Reference and Fragment Reference let you create relationships to other content within AEM. This means you can realize headless delivery of. Next, explore the power of AEM’s GraphQL API using the built-in GraphiQL IDE. With Headless Adaptive Forms, you can streamline the process of building. In the download dialog box, select the download options that you want. With Headless Adaptive Forms, you can streamline the process of building. js and click on the Install option. Example applications are a great way to explore the headless capabilities of Adobe Experience Manager (AEM). A Content author uses the AEM Author service to create, edit, and manage content. cors. 2. The Story So Far. Start here for a guided journey through the powerful and flexible headless features of AEM, their capabilities, and how to leverage them on your project. The JSON content is then consumed by the single-page app, which has been integrated with the AEM JS SDK. Headful and Headless in AEM; Headless Experience Management. In the second step, you map your UI components or use a public UI components library, such as Google Material UI or Chakra UI to style your forms. Learn about headless technologies, what they bring to the user experience, how AEM supports headless models, and how to implement your own headless development project from A to Z. Welcome to the documentation for developers who are new to Adobe Experience Manager headless CMS! Learn about the powerful and flexible headless features, their capabilities, and how to use them on your first headless development project. The session will be split in two halves as follows: Part 1: AEM as a headless CMS Where/When/Why? Presenter: Vengadesh Shanmugavelu - Technical Architect, Qatar Airways. With Adobe Experience Manager (AEM), you can selectively access your Content Fragments, using the AEM GraphQL API, to return only the content that you need. The following AEM documentation includes everything from essential guides for those new to the content management system (CMS) to videos, tutorials, and further learning resources to get the most out of AEM 6. There is a context. AEM’s WCM Core Components have built-in functionality to support a normalized JSON schema of exported Pages and Components. e. 4. A modern content delivery API is key for efficiency and performance of Javascript-based frontend applications. Learn the basic of modeling content for your Headless CMS using Content Fragments. The journey defines additional personas with which the developer must interact for a successful project, but the point-of-view for the journey is that of the developer. Below is a simple path for creating, managing, and delivering experiences using AEM as a Cloud Service in five steps for users who are already familiar with AEM and headless technology. ; The Fragment Reference data type lets you. It gives developers some freedom (powered by a. Body is where the content is stored and head is where it is presented. Developer. An end-to-end tutorial illustrating how to build-out and expose content using AEM Headless. The code is not portable or reusable if it contains static references or routing. A “headless” CMS is a content management system that lets you take content from a CMS and deliver it to any front end using any framework of choice. The exact steps of your transition to Cloud Service depend on the systems you have purchased and the software development life-cycle practices you follow. Adobe Experience Manager Sites is the industry-leading content management system that empowers any marketer or developer to create high-performance pages across any digital property — from web to mobile to apps. In this session we will cover Adobe Experience Manager fluid experiences and its application in managing content and experiences for either headful or headless CMS scenarios. AEM provides a Translation Integration Framework for headless content, allowing Content Fragments and supporting assets to be easily translated for use across locales. Considering the importance of SPA, now the focus is more on SPA with CMS — Consume the content from CMS systems to enable the SPA experience to end-users. Understand Headless in AEM; Learn about CMS Headless Development; Getting Started with AEM Headless as a Cloud Service; Path to your first experience using AEM Headless; How. There are many ways by which we can implement headless CMS via AEM. Using a REST API introduce. By adding the Adobe Target extension to Experience Platform Launch, you can use the features of Adobe Target on AEM web pages. The typical use case being our clients have a complete AEM suite and we would like to pull down assets within the CMS for them to use within our application. AEM Headless Content Author Journey - Overview; Authoring for Headless with AEM - An Introduction; Authoring Basics for Headless with AEM; Learn about using references in Content Fragments; Learn about defining Metadata and Tagging for Content Fragments; Implementing. Tap the Local token tab. The session will be split in two halves as follows: Part 1: AEM as a headless CMS Where/When/Why? Presenter: Vengadesh Shanmugavelu - Technical Architect, Qatar Airways. Notice the configuration window with the Target account credentials imported, and. Build a React JS app using GraphQL in a pure headless scenario. If auth is not defined, Authorization header will not be set. Permissions and personas can broadly be considered based on the AEM environment Author or Publish. Learn how the Universal Editor enables what-you-see-is-what-you-get (WYSIWYG) editing of any headless and headful experience. Adobe Experience Manager headless CMS is the most flexible content management system that helps teams quickly build and deliver customer experiences across all channels and devices. With Headless Adaptive Forms, you can streamline the process of. You also learn how you can create editable SPAs using AEM's SPA Editor framework, and integrate external SPAs, enabling editing capabilities as required. Headless. Then the Content Fragments Models can be created and the structure defined. Overview. The ImageRef type has four URL options for content references: _path is the referenced path in AEM. Tech StackExample applications are a great way to explore the headless capabilities of Adobe Experience Manager (AEM). Developers using the React framework create a SPA and then map areas of the SPA to AEM components, allowing authors to use familiar AEM Sites editing tools. Session description: There are many ways by which we can implement. This involves structuring, and creating, your content for headless content delivery. 2. Due to this approach, a headless CMS does not. An end-to-end tutorial illustrating how to build-out and expose content using AEM Headless. Headless CMS. The Create new GraphQL Endpoint dialog box opens. This involves structuring, and creating, your content for headless content delivery. A modern content delivery API is key for efficiency and performance of Javascript-based frontend applications. Adobe Experience Manager supports a headless approach, freeing it from being bound to its historical Java-based web development. Multiple requests can be made to collect as many results as required. These are self-contained items of content that can be directly accessed by a range of applications, as they have a predefined structure, based on Content Fragment Models. With Adobe Experience Manager version 6. The power of AEM allows it to deliver content either headlessly, full-stack, or in both. An introduction to using the features of Adobe Experience Manager as a Cloud Service as a Headless CMS to author content for your project. Created for: Beginner. This Android application demonstrates how to query content using the GraphQL APIs of AEM. Persisted GraphQL queries. Start here for a guided journey through the powerful and flexible headless features of AEM, their capabilities, and how to leverage them on your project. We’re excited to tell you about Adobe Developers Live, a one-day online event all about Adobe Experience Manager. GraphQL Model type ModelResult: object . Adobe Experience Manager helps you create next-generation digital experiences for your users and it keeps getting better with new features and developer capabilities to meet your needs. While client-side GraphQL queries can also be executed using HTTP POST requests, which cannot be cached, persisted queries can. Learn how to use Content Fragments in Adobe Experience Manager (AEM) as a Cloud Service with the AEM GraphQL API for headless content delivery. This approach enables the CMS to live up to the promise of managing content in place and publishing anywhere. Scheduler was put in place to sync the data updates between third party API and Content fragments. The AEM Headless Client for Java is used to execute the GraphQL queries and map data to Java objects to. AEM offers an out of the box integration with Experience Platform Launch. 5. From here, you can move over to the Content section {1}, where you can manage all of the content that exists in the newly created space. The context. Adobe Experience Manager. Contributions are welcome! Read the Contributing Guide for more information. 1 Answer. Content creation. Enable developers to add automation. All of the WKND Mobile components used in this. Translating Headless Content in AEM. Adobe Experience Manager headless CMS gives you all the tools you need to manage your content and make it available via APIs to any number of front ends via both JSON and GraphQL. Persisted queries are queries that are stored on the Adobe Experience Manager (AEM) server. To get your AEM headless application ready for. Understand Headless in AEM; Learn about CMS Headless Development; Getting Started with AEM Headless as a Cloud Service; Path to your first experience using AEM Headless; How. The option Enable model is activated by default. This guide describes how to create, manage, publish, and update digital forms. Or in a more generic sense, decoupling the front end from the back end of your service stack. Persisted queries are queries that are stored on the Adobe Experience Manager (AEM) server. Or in a more generic sense, decoupling the front end from the back end of your service stack. Headless CMS. A primary use case for The Adobe Experience Manager as a Cloud Service (AEM) GraphQL API for Content Fragment Delivery is to accept remote queries from third-party applications or services. So what is AEM? First and foremost, AEM is a Content Management System with a wide range of features that can also be customized to meet your requirements. Using headless e-commerce allows you to separate the CMS from the e-commerce engine part. Translating Headless Content in AEM. Contentful provides unlimited access to platform features and capabilities — for free. To accelerate the tutorial a starter React JS app is provided. Headless-cms-in-aem Headless CMS in AEM 6. In terms of authoring Content Fragments in AEM this means that:Meet the headless CMS that powers connected experiences everywhere, faster. In addition to offering robust tools to create, manage, and deliver traditional webpages in the full-stack fashion, AEM also offers the ability to author self-contained selections of content and serve them headlessly. The other fields were added automatically by AEM, and represent helpful methods to provide information about a certain Content Fragment; in this example, (the helper fields) _path, _metadata, _variations. Adobe Experience Manager (AEM) is the leading experience management platform. The following AEM documentation includes everything from essential guides for those new to the content management system (CMS) to videos, tutorials, and further learning resources to get the most out of AEM 6. The TagID is added to the content node’s cq:tags property and resolves to a node of type cq:Tag. References to other content, such as images or other Content Fragments can be dynamically inserted in-line within the flow of the text. Accelerates project development with AEM Core Components, AEM Venia reference storefront, AEM Project Archetype, and integration patterns for PWAs (Headless content & commerce). Translating Headless Content in AEM. The session will be split in two halves as follows: Part 1: AEM as a headless CMS Where/When/Why? Presenter: Vengadesh Shanmugavelu - Technical Architect, Qatar Airways. This article describes how to work with large results in AEM Headless to ensure the best performance for your application. Digital asset management. With these operations the API lets you operate Adobe Experience Manager as a Cloud Service as a headless CMS (Content Management. Getting Started with AEM Headless as a Cloud Service. These remote queries may require authenticated API access to secure headless content delivery. 0 versions enable the GraphQL runtime platform to expose the Content Fragments through GraphQL API. Release Notes. You also learn how you can create editable SPAs using AEM’s SPA Editor framework, and integrate external SPAs, enabling editing capabilities as required. Content Models serve as a basis for Content. Understand Headless in AEM; Learn about CMS Headless Development; Getting Started with AEM Headless as a Cloud Service; Path to your first experience using AEM Headless; How to model your content as AEM Content Models; How to access your content via AEM delivery APIs; How to update your content via AEM Assets APIs; How. Select Edit from the mode-selector in the top right of the Page Editor. Secure and Scale your application before Launch. 1. This allows the marketing team to use their favorite CMS tool, and at the same time, you can use the engine with the most features. supports headless CMS scenarios where external client applications render experiences using content managed in AEM. This guide provides important information about the latest release of Experience Manager as a Cloud Service, including what’s new deprecated and removed features, and known issues. Developer. The creation of a Content Fragment is presented as a wizard in two steps. Configure the Translation Connector. A DXP is the full suite of tools powering the delivery of personalized. Content models. 10. 4. This provides the user with highly dynamic and rich experiences. AEM’s GraphQL queries can be written to provide URLs to images based on where the image is referenced from. supports headless CMS scenarios where external client applications render experiences using content managed in AEM. 4. Explore tutorials by API, framework and example applications. This tutorial explores how AEM’s GraphQL APIs and headless capabilities can be used to power the experiences surfaced in an external app. “Adobe Experience Manager is at the core of our digital experiences. A Headless Content Management System (CMS) is a back-end only content management system, designed and built explicitly as a content repository that makes content accessible via an API, for display on any device. See generated API Reference. ” Tutorial - Getting Started with AEM Headless and GraphQL. Navigate to Tools, General, then select GraphQL. The Story So Far. Authoring for AEM Headless as a Cloud Service - An Introduction: An introduction to the headless features of Adobe Experience Manager as a Cloud Service, and how to author content for your project. For reference, the context. In this part of the AEM Headless Developer Journey, learn about what is required to get your own project started with AEM Headless. The HTTP GET requests from the headless app to AEM’s GraphQL APIs must be configured to interact with the correct AEM service, as. From the program overview page in Cloud Manager, tap or click on the link to the AEM authoring environment. Rich text with AEM Headless. Lastly, the context. Learn about the concepts and mechanics of authoring content for your Headless CMS using Content Fragments. Permissions and personas can broadly be considered based on the AEM environment Author or Publish. This architecture diagram shows various components of a headless and conventional CMS. Content Fragments Support in AEM Assets HTTP API feature helped us to solve the multiple challenges and provide a seamless headless delivery. A Headless Content Management System (CMS) is a back-end only content management system, designed and built explicitly as a content repository that makes content accessible via an API, for display on any device. The AEM SDK. How to Create Single Page Applications (SPAs) with AEM. The Assets REST API offered REST-style access to assets stored within an AEM instance. In the previous document of the AEM Sites translation journey, Get started with AEM Sites translation you learned how to organize your content and how AEM’s translation tools work and you should now: Understand the importance of content structure to translation. Select the Configure button. 8. Developer. Getting Started with AEM Headless - GraphQL by Adobe Docs Abstract AEM’s GraphQL APIs for Content Fragments supports headless CMS scenarios where external client applications render experiences using content managed in AEM. Objective. The response of a GET request can be cached at the Dispatcher and Content Delivery Network (CDN) layers, ultimately. 5 and Headless. Understand Headless in AEM; Learn about CMS Headless Development; Getting Started with AEM Headless as a Cloud Service; Path to your first experience. For the translation specialist, the same set of translation tools can be applied to both types of content, giving you a unified approach for translating your content. Adobe Experience Manager, a widely recognized CMS, provides a comprehensive suite of features and capabilities that make it an attractive choice for implementing Headless CMS solutions. They can be requested with a GET request by client applications. Persisted queries are GraphQL queries that are created and stored on the Adobe Experience Manager (AEM) server. The auto-generated AEM page must have its type changed to Remote SPA page , rather than a SPA page . AEM Headless is a CMS solution from Experience Manager that allows structured content (Content Fragments) in AEM to be consumed by any app over HTTP using GraphQL. The Story So Far. Build from existing content model templates or create your own. styling it, presenting it, and delivering it all happen in AEM. Learn how to publish your translated content and update the translations as the content updates. Tap Get Local Development Token button. This is the same framework used to translate other AEM content, such as Pages, Experience Fragments, Assets, and Forms. An AEM project is required to setup-supporting configuration and content requirements to allow AEM SPA Editor to author a Remote SPA. This guide contains videos and tutorials on the many features and capabilities of AEM. Creating Content Fragment Models. js application demonstrates how to query content using AEM’s GraphQL APIs using persisted queries. 3 latest capabilities that enable channel agnostic experience management use-cases. CIF is built for continuous innovation with an always up-to-date add-on, allowing customer to access new and improved features. The benefit of this approach is cacheability. Let teams author pages with familiar tools like Microsoft Word or Google Docs. It contains the following artifacts: The Quickstart jar - an executable jar file that can be used to set up both an author and a publish instance. Explore tutorials by API, framework and example applications. Permission considerations for headless content. “Adobe Experience Manager is at the core of our digital experiences. The multi-line text field is a data type of Content Fragments that enables authors to create rich text content. Learn how to create a SPA using the React JS framework with AEM's SPA Editor. To manage permissions of groups in AEM, navigate to Tools > Security > Permissions. Learn how to create a SPA using the React JS framework with AEM's SPA Editor. Adobe Experience Manager connects digital asset management, a powerful content. Provide a Model Title, Tags, and Description. You signed out in another tab or window. CMS Headles | Headless CMS with AEM: A Complete Guide by One-inside Abstract You might have already heard about Headless CMS and you may be wondering if you should. Overview. The <Page> component has logic to dynamically create React components based on the. AEM Forms Headless Adaptive Forms provide a fast and efficient way to create forms for various platforms including Headless or Headful CMS, React applications, Single Page Applications (SPA), Web Apps, Mobile apps, Amazon Alexa, Google Assistant, WhatsApp, and more. They allow you to prepare content ready for use in multiple locations/over multiple channels, ideal for headless delivery. GraphQL, an industry standard, application-agnostic query language to retrieve content, lets developers get exactly the content they need —. An introduction to the headless features of Adobe Experience Manager, and how to author content for your project. The GraphiQL tool enables developers to create and test queries against content on the current AEM environment. Virtual Event - AEM GEMs feature two of our customers presenting a technical deep dive session on the usage of AEM as Headless. A hybrid CMS is a “halfway” solution. Learn how Sitecore customers are using cutting-edge. Welcome to this tutorial chapter where we will explore configuring a React app to connect with Adobe Experience Manager (AEM) Headless APIs using the AEM Headless SDK. In the second step, you map your UI components or use a public UI components library, such as Google Material UI or Chakra UI to style your forms. Content Models are structured representation of content. While client-side GraphQL queries can also be executed using HTTP POST requests, which cannot be cached, persisted. Last update: 2023-10-04. This guide contains videos and tutorials on the many features and capabilities of AEM. The platform is also extensible, so you can add new APIs in the future to deliver content in a different. For now, the focus is on putting the right people in the right jobs to help drive your Adobe Experience Manager deployment. Select the Extension Catalog option, and search for Target in the filter. In this optional continuation of the AEM Headless Developer Journey, you learn how AEM can combine headless delivery with traditional full-stack CMS features. This shows that on any AEM page you can change the extension from . With Headless Adaptive Forms, you can streamline the process of building. This approach enables the CMS to live up to the promise of managing content in place and publishing anywhere. AEM Headless APIs allow accessing AEM content from any. An end-to-end tutorial. The JSON content is then consumed by the single-page app, which has been integrated with the AEM JS SDK. Each environment contains different personas and with. Ensure you adjust them to align to the requirements of your. This means you can realize headless delivery of structured. In this post, Adobe Experience Cloud introduces its Adobe Experience Manager Headless Extension for PWA Studio that enables developers to leverage headless. Content creation. Our previous CMS was older, slower and more difficult to manage, which gave our global team little flexibility. In previous releases, a package was needed to install the GraphiQL IDE. 0 or later Included in the WKND Mobile AEM Application Content Package below; Prior to starting this tutorial ensure the following AEM instances are installed and running on your local machine:. In the previous document of the AEM headless journey, Getting Started with AEM Headless as a Cloud Service you learned the basic theory of what a headless CMS is and you should now: Understand the basics of AEM’s headless features. Be aware of AEM’s headless integration levels. The two only interact through API calls. The journey defines additional personas with which the developer must interact for a successful project, but the point-of-view for the journey is that of the developer. 5 or later; AEM WCM Core Components 2. This React application demonstrates how to query content using AEM’s GraphQL APIs using persisted queries. Navigate to the assets that you want to download. Select the folder or select one or more assets within the folder. It is a traditional, monolithic CMS with a content-as-a-service (CaaS) API. First select which model you wish to use to create your content fragment and tap or click Next. 1. Headless Setup. Looking at this at a high level, AEM at the bottom of the stack, will act as a headless CMS and expose content as JSON using AEM Content Services APIs. This provides the user with highly dynamic and rich experiences. AEM provides a Translation Integration Framework for headless content, allowing Content Fragments and supporting assets to be easily translated for use across locales. This Next. Last update: 2023-08-31. In this tutorial, you learn how to integrate the requests for persisted queries into the sample WKND GraphQL React app using the AEM Headless Client for JavaScript. storyblok. The AEM Headless SDK is set of libraries that can be used by clients to quickly and easily interact with AEM Headless APIs over HTTP. The following Documentation Journeys are available for headless topics. Content authors cannot use AEM's content authoring experience. Authors: Mark J. We’ll cover retrieving Content Fragment data from AEM’s GraphQL APIs and displaying it in the React app. Manage and serve content for any channel with a pure play agile headless CMS. This session will cover the following - Content services via exporter/servlets Content fragment via asset API (demo) Content fragment via Graphql (demo) Some real-time use cases around using content fragments and their approaches SPA. Create your first React Single Page Application (SPA) that is editable in Adobe Experience Manager AEM with the WKND SPA. Navigate to Tools, General, then select GraphQL. Headless and AEM; Headless Journeys. View the source code. In the previous document of the AEM headless journey, Getting Started with AEM Headless as a Cloud Service you learned the basic theory of what a headless CMS is and you should now: ; Understand the basics of AEM's headless features.