Adobe aem headless cms documentation. Editable templates and core components, such as headers and footers, with adjustable styling. Adobe aem headless cms documentation

 
 Editable templates and core components, such as headers and footers, with adjustable stylingAdobe aem headless cms documentation  With Headless Adaptive Forms, you can streamline the process of

The Navigation Panel can be opened by selecting Adobe icon at the top left,. 3. In a typical development cycle, you start with creating and hosting Headless adaptive forms on Adobe Experience Manager Forms Server. 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. Repeat above step for person-by-name query. Now even AEM as a cloud service has react as inbuilt program into its archetype as part of Adobe’s best practices known to its Headless CMS architecture. In this session, we will cover the following: Content services via exporter/servlets. In the Name field, enter AEM Developer Tools. Bring in-context and headless authoring to your NextJS app. 5 and Adobe Experience Manager as a Cloud Service, let's explore how Adobe Experience. Learn how to create a SPA using the React JS framework with AEM's SPA. 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. There are two types of updates, feature releases and maintenance releases: Feature releases are done with a predictable monthly frequency and are focused on new capabilities and product innovations. Then realize that the structure for Adobe Experience Manager (AEM) using Content Fragments Models and Content Fragments, for reuse across channels. In AEM, AEM Content fragments are headless with GraphQL, AEM JCR OOTB XML and JSON, Sling model Exporter, CCMS (XML Documentation Add-on for Adobe Experience Manager), and AEM SPA. If content is not fully cached, the CDN calls out (reverse proxy) to the Dispatcher. See full list on experienceleague. The Create new GraphQL Endpoint dialog box opens. Authoring for AEM Headless - An Introduction. Implementing User Guide. If you need AEM support to get started with AEM 6. 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. 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. This session will cover the following - Content services via exporter/servlets Content fragment via asset API (demo) Content fragment via Graphql (demo) Some real. Understand how to build and customize experiences using AEM’s powerful features by exploring these development and deployment topics. An introduction to the headless features of Adobe Experience Manager, and how to author content for your project. An Introduction to the Architecture of Adobe Experience Manager as a Cloud Service - Understand AEM as a Cloud Service’s structure. Define the trigger that will start the pipeline. Start here for a guided journey through the powerful and flexible headless features of AEM, their capabilities. Navigate to the required folder and select Create: Select Experience Fragment to open the Create Experience Fragment wizard. Tutorials by framework. With Adobe Experience Manager as a Cloud Service (AEM) you can create a selection of content, then specify which audiences (groups of end-users) see each individual experience. AEM provides a Translation Integration Framework for headless content, allowing Content Fragments and supporting assets to be easily translated for use across locales. This document helps you understand headless content. Customers move constantly between multiple devices and platforms when interacting with brands today, and they expect those experiences to be seamless. Explore the power of a headless CMS with a free, hands-on trial. A collection of documentation journeys describing how to use Adobe Experience Manager as a Headless CMS. jar file, perform the. Since the cloud service auto-scales within seconds, and new features are added continuously, this frees up significant IT resources. With GraphQL for Content Fragments available for AEM 6. The use of Android is largely unimportant, and the consuming mobile app could be written in any. In this part of the AEM Headless Developer Journey, learn about what is required to get your own project started with AEM Headless. 5. AEM as a Cloud Service GraphQL API used with Content Fragments is heavily based on the standard, open source GraphQL API. The diagram above depicts this common deployment pattern. Last update: 2023-08-16. Understand headless translation in AEM; Get started with AEM headless translation Adobe Experience Manager (AEM), can selectively access your Content Fragments using the AEM GraphQL API, to return only the content that is needed. Content Fragments and Experience Fragments are different features within AEM:. GraphQL is used in two (separate) scenarios in Adobe Experience Manager (AEM): AEM Commerce consumes data from a Commerce platform via GraphQL. The tagged content node’s NodeType must include the cq:Taggable mixin. 1. json (or . If the image is purely decorative and alternative text would be unnecessary, the Image is decorative option can be checked. Last update: 2023-08-31. jcr. Clients can send an HTTP GET request with the query name to execute it. An introduction to the powerful, and flexible, headless features of Adobe Experience Manager, and how to author content for your project. 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. Content Services: Expose user defined content through an API in JSON format. infinity. One of the major goals for AEM as a Cloud Service is to allow experienced customers (having used AEM either on-premise or in the context of the Adobe Managed Services) to migrate to AEM as a Cloud Service as. Learn about the concepts and mechanics of authoring content for your Headless CMS using Content Fragments. the website) off the “body” (the back end, i. Select Create. With Headless Adaptive Forms, you can streamline the process of building. Last update: 2023-08-31. Authoring Basics for Headless with AEM. Learn how features like Content Fragment Models, Content Fragments, and a GraphQL API are used to power headless experiences. location). In this session, you’ll learn how to quickly setup a. apache. 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. This React application demonstrates how to query content using AEM’s GraphQL APIs using persisted queries. Referrer Filter. The America’s AEM Expert Solution Consulting Team is growing. The Create new GraphQL Endpoint dialog box opens. 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. Experience League. Watch overview At One Inside, our expertise relies on the implementation of the Adobe CMS, Adobe Experience Manager (AEM). The tagged content node’s NodeType must include the cq:Taggable mixin. Francisco Chicharro Sanz, Software Engineer, Adobe & Tobias Reiss, Engineering Manager, Adobe. PGA TOUR joins us to discuss key insights and best practices that helped them build a new multichannel experience for golf fans worldwide. References to other content, such as images or other Content Fragments can be dynamically inserted in-line within the flow of the text. Within a model: Data Types let you define the individual attributes. This guide explains the concepts of authoring in AEM in the classic user interface. Navigate to Tools -> Assets -> Content Fragment Models. Learn how Experience Manager as a Cloud Service works and what the software can do for you. See Wikipedia. Learn about Creating Content Fragment Models in AEM The Story so Far. The Standard Tags tab is the default namespace, which means there is no. Scheduler was put in place to sync the data updates between third party API and Content fragments. Headless is an example of decoupling your content from its presentation. This document helps you understand headless content delivery, how AEM supports headless, and how. AEM offers the flexibility to exploit the advantages of both models in one project. In a production environment, you use AEM Forms to deliver the form JSON, more on it later. Now that you have completed this part of the AEM Headless Developer Journey, you should: Understand important planning considerations for designing your content. It illustrates how multiple features work together to solve a business need in a best practices fashion. Navigate to Tools, General, then open Content Fragment Models. How do they work? What are the alternatives and differences? Why would you want to use a. ) that is curated by the. Release Notes. This shows that on any AEM page you can change the extension from . From the main menu of AEM, tap or click on Sites. The TagID is added to the content node’s cq:tags property and resolves to a node of type cq:Tag. Documentation. The AEM Headless Client for JavaScript is used to execute the GraphQL persisted queries that power the app. AEM as a Cloud Service lets you capitalize on the AEM applications in a cloud-native way, so that you can: Scale your DevOps efforts with Cloud Manager: CI/CD framework, autoscaling, API connectivity, flexible deployment modes, code quality gates, service delivery transparency, and guided updates. These are defined by information architects in the AEM Content Fragment Model editor. There are many ways by which we can implement headless CMS via AEM. This involves structuring, and creating, your content for headless content delivery. 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. Adobe Experience Manager supports a headless approach,. Introduction to Adobe Experience Manager headless CMS Content Fragments GraphQL capabilities. The Story So Far At the beginning, Learn About CMS Headless Development covered headless content delivery and why it should be used. Content is added using components (appropriate to the content type) that can be dragged onto the page. A headless CMS is therefore responsible for the (backend) content management services, together with the mechanisms allowing the (frontend) applications to access that content. . Wrap the React app with an initialized ModelManager, and render the React app. ; The Fragment Reference data type lets you realize multiple levels. Adobe Experience Manager Forms as a Cloud Service is a cloud-native solution for businesses to create, manage, publish, and update complex digital forms and communications while integrating submitted data with back-end processes, business rules, and saving data in an external data store. Adobe’s Open Web stack, providing various essential components (Note that the 6. We can show you what AEM can do in regards to content. AEM Content Fragments work together with the AEM GraphQL API (a customized implementation, based on standard GraphQL), to deliver structured content for use in. json to be more correct). Headless implementation forgoes page and component management, as is traditional in. This document. For example, when the resolution goes below 1024. The headless part is the content backend, as 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 data types Content Reference and Fragment Reference let you create relationships to other content within AEM. Content Fragment Models are generally stored in a folder structure. This React application demonstrates how to query content using AEM’s GraphQL APIs using persisted queries. Introduction AEM has multiple options for defining. Once your page is created (either new or as part of a launch or live copy) you can edit the content to make the updates you require. A collection of documentation journeys describing how to use Adobe Experience Manager as a Headless CMS. The AEM Headless Client for JavaScript is used to execute the GraphQL persisted queries that power the app. Select the Configure button. Why would you need a headless CMS? IT is looking to address Agility and Flexibil. To tag content and use the AEM Tagging infrastructure : The tag must exist as a node of type cq:Tag under the taxonomy root node. Experience League | Community. Welcome to the multi-part tutorial for developers looking to augment an existing React-based (or Next. Open the required model for Edit; use either the quick action, or select the model and then the action from the toolbar. in our case it will be AEM but there is no head, meaning we can decide the head on our own. For an overview of how a simple SPA in AEM is structured and how it works, see the getting started guide for both React and Angular. AEM Headless GraphQL Video Series Learn about AEM’s GraphQL capabilities through the in-depth walk-through of Content Fragments and and AEM’s GraphQL APIs and development tools. Adobe Experience Manager’s Referrer Filter enables access from third-party hosts. json (or . Consider which countries share languages. Created for: Beginner. Authoring for AEM Headless - An Introduction. The Android Mobile App. To maintain version history of assets in AEM, configure asset versioning in AEM. Instead, you control the presentation completely with your own code. ,. JANUARY 2019 | The hybrid architecture of Adobe Experience Manager 5 Headless CMS architecture The term headless originates from the idea that the front-end presentation layer is the “head” of the application. this often references a page in the documentation. AEM 6. Adobe Experience Manager, the leading headless CMS* by Adobe Abstract Adobe Experience Manager is a headless CMS, who knew? Let's explore why organisations are evaluating headless content delivery and how AEM can help. The UI caters for both mobile and desktop devices, though rather than creating two styles, AEM uses one style that works for all screens and devices. Create a client that calls the JobManager. Understand Headless in AEM; Learn about CMS Headless Development;. The term “headless” comes from the concept of chopping the “head” (the front end, i. The Wizard opens. This React application demonstrates how to query content using AEM’s GraphQL APIs using persisted queries. The best practice is a language-based structure with no more than 3 levels between the top-level authoring and country sites. Understand headless translation in AEM; Get started with AEM headless. This document helps you understand the AEM headless publication pipeline and the performance considerations you must be aware of before you go live with your application. All 3rd party applications can consume this data. Headless and AEM; Headless Journeys. Learn how to create a SPA using the React JS framework with AEM's SPA Editor. In Headless CMS the body remains constant i. These remote queries may require authenticated API access to secure headless content. The creation of a Content Fragment is presented as a wizard in two steps. 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. Headless is an example of decoupling your content from its presentation. See Viewing Cloud Manager’s. Iryna Lagno, Engineering Manager, Adobe & Duy Nguyen, Software Engineer, Adobe. API. With these operation the API lets you operate Adobe Experience Manager as a headless CMS (Content Management System) by providing Content Services to a. 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. In the last step, you fetch and. Use a language/country site naming convention that follows W3C standards. Confirm with Create. Content Services: Expose user defined content through an API in JSON format. Using a REST API introduce challenges: Large number of requests for fetching one object at a time Often “over-delivering” content, meaning the application receives more than it needs To overcome these challenges GraphQL provides a query-based API allowing clients to query AEM for only the content it needs, and to receive using a single API. Experience Manager fast tracks new apps and digital experience development using a scalable, cloud-native CMS using open, extensible APIs. 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. HubSpot doesn’t have designed instruments for headless development. So in this regard, AEM already was a Headless CMS. Start here for a guided journey through the powerful and flexible headless features of AEM, their capabilities, and how to use them on your project. HubSpot doesn’t have designed instruments for headless development. Secure and Scale your application before Launch. Confirm with Create. 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. Moving to AEM as a Cloud Service: Understand the transition journey to Cloud Service. Adobe Experience Manager as a Headless CMS - Where/When/Why?In this session, you'll learn how to implement headless CMS via Adobe Experience Manager in many ways. This user guide contains videos and tutorials helping you maximize your value from AEM. Objective This document helps you understand headless content delivery and why it should be used. In this part of the AEM Headless Content Architect Journey, you can learn the (basic) concepts and terminology necessary to understand content modeling when using Adobe Experience Manager (AEM) as a Cloud Service as a Headless CMS. To apply pre-defined tags, in the Page Properties window use the Tags field and the Select Tags window. AEM offers the flexibility to exploit the advantages of both models in one project. . Readers new to AEM. Introduction. 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. Translating Headless Content in AEM. 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. See Wikipedia. Adobe Experience Manager projects can be implemented in both headful and headless models, but the choice is not binary. Why would you want to use a Headless CMS? Learn about Headless CMS. Meet our community of customer. Headful and Headless in AEM; Headless Experience Management. What Is Adobe AEM? Adobe AEM is a powerful CMS used to create, edit, and manage digital content across various channels. Meet our community of customer. Additional. The user-friendly setup makes it easy for anyone to use, thanks to its: What you see is what you get (WYSIWYG) editor. Documentation. Headless CMS advantages: • Scales efficiently to multiple channels and unlocks. Above the Strings and Translations table, click Add. ; The Fragment Reference data type lets you realize multiple levels of. User. Description. The Standard Tags tab is the default namespace, which means there is no. 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. Consider which countries share languages. To determine the correct approach for managing build dependent configurations, reference the AEM Headless app’s framework (for example, React, iOS, Android™, and so on) documentation, as the approach varies by. In the author environment, authors may apply tags by accessing the page properties and entering one or more tags in the Tags/Keywords field. I'm looking for specific HTTP RESTful API documentation for AEM Assets headless-CMS. Customers move constantly between multiple devices and platforms when interacting with brands today, and they expect those experiences to be seamless. Introduction to AEM Forms as a Cloud Service. This tutorial explores how AEM’s GraphQL APIs and headless capabilities can be used to power the experiences surfaced in an external app. Then Getting Started with AEM Headless as a Cloud Service described AEM Headless in the context of your own project. cors. This document helps you understand how to get started translating headless content in AEM. AEM as a Cloud Service GraphQL API used with Content Fragments is heavily based on the standard, open source GraphQL API. With Headless Adaptive Forms, you can streamline the process of building forms, making it easier to collect data from your users. With Headless Adaptive Forms, you can streamline the process of. Experience League. Headless Developer Journey: Explore this guided journey through the powerful and flexible headless features of AEM to prepare for your first headless project. Last update: 2023-03-03. Topics: Content Fragments. Allowing for bulk delivery of exactly what is needed for rendering as the response to a single API query. Experience Manager tutorials. This shows that on any AEM page you can change the extension from . It extends Adobe Experience Manager as a. 5 Developing Guide Accessing and Delivering Content Fragments Headless Quick Start Guide. So in this regard, AEM already was a Headless CMS. Select Save & Close. js and click on the Install option. Becker (@ MarkBecker), Markus Haack (@ mhaack), and Jody Arthur This is the first part of a series of the new headless architecture for Adobe Experience Manager. AEM Fluid Experiences for headless usecases. This multi-part tutorial walks through the implementation of a React application for a fictitious lifestyle brand, the WKND. . 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. SPA Editor learnings. 5 and Headless. Product abstractions such as pages, assets, workflows, etc. The Story So Far. Notice the configuration window with the Target account credentials imported, and. Rather than delivering HTML or formatted content directly, a headless CMSWithin a model: Data Types let you define the individual attributes. 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. 03-31-2023. Headless is an example of decoupling your content from its presentation. Tap the checkbox next to My Project Endpoint and tap Publish. supports headless CMS scenarios where external client applications render experiences using content managed in AEM. Using a REST API introduce challenges: 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. Watch Adobe’s story. The two only interact through API calls. There are various forms of non-text content, so the value of the text alternative depends on the role the graphic plays in the. With the power of Adobe's headless CMS capabilities, brands can build and deliver dynamic, connected experiences across any touchpoint faster. “We use Adobe Experience Manager as a headless CMS because it provides maximum flexibility and future-proofs our content. From the AEM Start screen, navigate to Tools > General > GraphQL Query Editor. An introduction to the headless features of Adobe Experience Manager, and how to author content for your project. The power of AEM allows it to deliver content either headlessly, full-stack, or in both. 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. In this case, /content/dam/wknd/en is selected. In the Source tab, select a template: When you select an Editable template, a theme and submit action specified in the template are auto-selected, and the Create button is enabled. AEM Headless APIs allow accessing AEM. A totally different front end uses AEM Templates, which in turn invokes AEM components,. To determine the correct approach for managing. The use of Android is largely unimportant, and the consuming mobile app. Create your first React Single Page Application (SPA) that is editable in Adobe Experience Manager AEM with the WKND SPA. We're trying to integrate AEM with a CMS too. We can show you what AEM can do in regards to content delivery — and in which case headless is recommended. With these operation the API lets you operate Adobe Experience Manager as a headless CMS (Content Management System) by providing. Start here for a guided journey through the powerful and flexible headless features of AEM, their capabilities, and how to leverage them on your first development project. So in this regard, AEM already was a Headless CMS. In the previous document of the AEM headless translation journey, Learn about headless content and how to translate in AEM you learned the basic theory of what a headless CMS is and you should now: Understand the basic. React App. Rich text with AEM Headless. Learn about key AEM 6. Within a model: Data Types allow you to define the individual attributes. Populates the React Edible components with AEM’s content. Chapter 7 of the tutorial uses a native Android Mobile App to consume content from AEM Content Services. Learn about the concepts and mechanics of authoring content for your Headless CMS using Content. The Assets REST API offered REST-style access to assets stored within an AEM instance. Iryna Lagno, Engineering Manager, Adobe & Duy Nguyen, Software Engineer, Adobe. Navigate to <aem install directory>/crx-quickstart/install folder. Developers need to ensure that their documentation is clear and concise to help other developers understand how the application works. This is achieved using Content Fragments, together with the AEM GraphQL API (a customized implementation, based on standard GraphQL), to headlessly deliver structured content. Headless CMS with AEM Content Fragments and Assets. This is the same framework used to translate other AEM content, such as Pages, Experience Fragments, Assets, and Forms. AEM requires the Alternative Text field to be filled by default. Problem here is, We have RTE fields across our site. In terms of. Tap in the Integrations tab. The Story So Far. Here you can specify: Name: name of the endpoint; you can enter any text. Learn about headless development using Adobe Experience Manager (AEM) as a Headless CMS. 3 and has improved since then, it mainly consists of the following components: 1. - Adobe Experience League Community - 551540 Headless CMS with AEM Content Fragments. Understand the steps to implement headless in AEM. Start here for a guided journey through the powerful and flexible headless features of AEM, their capabilities, and how to leverage them on your first development project. In Eclipse, open the Help menu. Headless Authoring Journey - Start here for a guided journey through the powerful and flexible headless features of AEM, their capabilities, and how. Or in a more generic sense, decoupling the front end from the back end of your service stack. Creating a Configuration. The TagID is added to the content node’s cq:tags property and resolves to a node of type cq:Tag. Documentation. Product abstractions such as pages, assets, workflows, etc. Learn how to use features like Content Models, Content Fragments, and a GraphQL API to power headless content delivery. The Content author and other. What is Adobe Experience Manager Headless CMS? Adobe Experience Manager headless CMS gives developers the freedom to do what they do best: build faster and deliver exceptional experiences using the languages, frameworks, and. Headless CMS. A Headless Content Management System (CMS) is: "A headless content management system, or headless CMS, is a back-end only content management system (CMS) built from the ground up as a content repository that makes content accessible via an API for display on any device. The Story So Far. Adobe Experience Manager supports a headless approach, freeing it from being bound to its historical Java-based web development. the content repository). Community. The React app should contain one instance of the <Page> component exported from @adobe/aem-react-editable-components. Hear from experts for an exclusive sneak peek. Overview. Content Services: Expose user defined content through an API in JSON format. In a bid to create the perfect, composable tech stack, headless implementations can end up as elaborate exercises that require connecting multiple teams, tools, and technologies. 1. In this post, Adobe Experience Cloud introduces its Adobe Experience Manager Headless Extension for PWA Studio that enables developers to leverage headless. Learn About CMS Headless Development by Adobe Docs Abstract In this part of the AEM Headless Developer Journey, learn about headless technology and why you would use it. For headless, your content can be authored as Content Fragments. A Title is mandatory. Log into AEM as a Cloud Service and from the main menu select Tools > General > Configuration Browser. Navigate to the folder holding your content fragment model. Content fragment via asset API (demo) Content fragment via graphql (demo) Some real-time use cases around using content fragments and their approaches. Since various solutions are used and there are several layers of monitoring, this page is organized into three sections:Introduction to AEM Forms as a Cloud Service. The most common deployment pattern with AEM headless applications is to have the production version of the application connect to an AEM Publish service. 3, Adobe has fully delivered its content-as-a-service (CaaS. On the Cloud Manager tile, select Launch. GraphQL is used in two (separate) scenarios in Adobe Experience Manager (AEM): AEM Commerce consumes data from a Commerce platform via GraphQL. Overview of Adobe Experience Platform integration with Eric Knee, Principal Enterprise Solution ArchitectThe new architecture supporting AEM as a Cloud Service involves some key changes to the overall developer experience. This involves structuring, and creating, your content for headless content delivery. Content Fragments Support in AEM Assets HTTP API feature helped us to solve the multiple challenges and provide a seamless headless delivery. A collection of documentation journeys describing how to use Adobe Experience Manager as a Headless CMS. With Adobe Experience Manager as a Cloud Service (AEM) you can create a selection of content, then specify which audiences (groups of end-users) see each individual experience. From the AEM Start screen, navigate to Tools > General > GraphQL. The best practice is a language-based structure with no more than 3 levels between the top-level authoring and country sites. Sign In. Previous page. Experience Cloud Advocates. Learn how to use Adobe Experience Manager (AEM) as a Headless CMS (Content Management System), with features such as Content Fragment Models, Content Fragments, and a GraphQL API that together power headless experiences at scale.