View the. This level of integration is the traditional headless model and allows your content authors to create content in AEM and deliver it heedlessly to any number of external services using GraphQL or to edit them from external services using the Assets API. 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. We’ll cover retrieving Content Fragment data from AEM’s GraphQL APIs and displaying it in the React app. The HTTP GET requests from the headless app to AEM’s GraphQL APIs must be configured to interact with the correct AEM service, as. The GraphiQL Explorer tool enables developers to create, and test queries against content on the current AEM environment. js implements custom React hooks. The configured AEM service’s host/domain is then used to construct the AEM GraphQL API URLs and Image URLs. All of the WKND Mobile components used in this. Example applications are a great way to explore the headless capabilities of Adobe Experience Manager (AEM). In the future, AEM is planning to invest in the AEM GraphQL API. 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. AEM Headless as a Cloud Service. Persisted queries are GraphQL queries that are created and stored on the Adobe Experience Manager (AEM) server. The GraphiQL Explorer tool enables developers to create, and test queries against content on the current AEM environment. Query for fragment and content references including references from multi-line text fields. See how AEM powers omni-channel experiences. We do this by separating frontend applications from the backend content management system. The AEM Headless Client for JavaScript is used to execute the GraphQL persisted queries that power the app. 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. Example applications are a great way to explore the headless capabilities of Adobe Experience Manager (AEM). Here you can specify: Name: name of the endpoint; you can enter any text. AEM Headless clients operating in a production capacity typically interact with AEM Publish, which contains the approved, published content. : Guide: Developers new to AEM and headless: 1. This tutorial uses a simple Node. In AEM 6. X) the GraphiQL Explorer (aka GraphiQL IDE) tool needs to be manually installed, follow instruction from here. Developers can use the JSON Preview in the Content Fragment editor to show all values of the current Content Fragment that can be returned using the GraphQL API. 5 the GraphiQL IDE tool must be manually installed. Content Fragments in Adobe Experience Manager (AEM) provide a structured approach to managing content. js (JavaScript) AEM Headless SDK for. Get started with Adobe Experience Manager (AEM) and GraphQL. In the previous document of the AEM headless journey, How to Access Your Content via AEM Delivery APIs you learned how to access your headless content in AEM via the AEM GraphQL API and you should now: Have a high-level understanding of GraphQL. Adobe Experience Manager Content Services leverages traditional Experience Manager Pages to compose headless REST API endpoints and Experience Manager Components to define or reference the content to expose on these endpoints. js application is invoked from the command line. Explore tutorials by API, framework and example applications. Topics: Content Fragments. Q: “How is the GraphQL API for AEM different from Query Builder API?” A: “The AEM GraphQL API offers total control on the JSON output, and is an industry standard for querying content. Enter the preview URL for the Content Fragment. Created for: Beginner. For publishing from AEM Sites using Edge Delivery Services, click here. In this part of the AEM Headless Developer Journey, learn how to use the REST API to access and update the content of your Content Fragments. Leverage your professional network, and get hired. The custom AEM headless client (api/Aem. Time; Headless Developer Journey: For users new to AEM and headless technologies, start here for a comprehensive introduction to AEM and its headless features from the theory of headless through going live with your first headless project. Dive into the details of the AEM GraphQL API. This guide uses the AEM as a Cloud Service SDK. js initializes and exports the AEM Headless Client used to communicate with AEM; src/api/usePersistedQueries. They can be used to access structured data, including texts, numbers, and dates, amongst others. js app. To learn more about authenticating requests to AEM as a Cloud Service, review the token-based authentication tutorial. By decoupling the CMS from the. The AEM Headless Client for JavaScript is used to execute the GraphQL persisted queries that power the app. The SPA is developed and managed externally to AEM and only uses AEM as a content API. AEM Headless as a Cloud Service. The HTTP GET requests from the headless app to AEM’s GraphQL APIs must be configured to interact with the correct AEM service, as. Example applications are a great way to explore the headless capabilities of Adobe Experience Manager (AEM). AEM Headless Developer Portal; Overview; Quick setup. The advanced tutorial illustrates in-depth aspects of working with Content Fragment Models, Content Fragments, and the AEM GraphQL persisted queries, including using the GraphQL persisted queries in a client application. 5 or later. “Adobe Experience Manager is at the core of our digital experiences. In a headless setup, the presentation system (the head) is decoupled from the content management (the tail). AEM Headless as a Cloud Service. npm module; Github project; Adobe documentation; For more details and code. Explore tutorials by API, framework and example applications. Created for: Beginner. We’ll cover retrieving Content Fragment data from AEM’s GraphQL APIs and displaying it in the React 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. In this part of the AEM Headless Developer Journey, learn how to use the REST API to access and update the content of your Content Fragments. jar) to a dedicated folder, i. js implements custom React hooks. The Single-line text field is another data type of Content. Developer. Here you can specify: Name: name of the endpoint; you can enter any text. AEM Headless as a Cloud Service. 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. js implements custom React hooks. AEM Headless Developer Portal; Overview; Quick setup. Learn about the various deployment considerations for AEM Headless apps. In this part of the AEM Headless Developer Journey, you can learn how to use GraphQL queries to access the content of your Content Fragments and feed it to your app (headless delivery). Tap or click Create. Objective. AEM Headless as a Cloud Service. Content models. Rich text with AEM Headless. Ensure you adjust them to align to the requirements of your project. Adobe Experience Manager Headless. After reading it, you can do the following:AEM Headless single-page app (SPA) deployments involve JavaScript-based applications built using frameworks such as React or Vue, that consume and interact with content in AEM in a headless manner. This simple React app uses the AEM Headless SDK to query AEM Headless APIs for an Adventure content, and displays the web-optimized image using img element with srcset and picture element. Developers can use the JSON Preview in the Content Fragment editor to show all values of the current Content Fragment that can be returned using the GraphQL API. It enables the initiation, management, and monitoring of content-related workflows. Learn to use modern front-end tools, like a webpack dev server, to rapidly develop the SPA against the AEM JSON model API. The API key is listed in developer console as the client ID. This server-side Node. Developer. The article contains recommendations, reference materials, and resources for developers of Assets as a Cloud Service. The HTTP GET requests from the headless app to AEM’s GraphQL APIs must be configured to interact with the correct AEM service, as. An end-to-end tutorial illustrating advanced concepts of Adobe Experience Manager (AEM) GraphQL APIs. The AEM Headless Client for Java is used to execute the GraphQL queries and map data to Java. Introduction to Adobe Experience Manager as a Headless CMS {#introduction-aem-headless} 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. The current implementation of the Assets HTTP API is based on the REST architectural style and enables you to access content (stored in AEM) via CRUD operations (Create, Read, Update, Delete). The following are examples of possible approaches for constructing URLs for AEM GraphQL API and image requests, for several popular headless frameworks and platforms. Cloud Service; AEM SDK; Video Series. The. js with a fixed, but editable Title component. TIP. The AEM Headless SDK is available for various platforms: AEM Headless SDK for client-side browsers (JavaScript) AEM Headless SDK for server-side/Node. We’ll cover retrieving Content Fragment data from AEM’s GraphQL APIs and displaying it in the React app. This simple React app uses the AEM Headless SDK to query AEM Headless APIs for an Adventure content, and displays the web-optimized image using img element with srcset and picture element. Learn how to integrate AEM Headless with Adobe Target, by exporting AEM Content Fragments to Adobe Target, and use them to personalize headless experiences using the Adobe Experience Platform Web SDK’s alloy. The srcset and sources use a custom setParams function to append the web-optimized delivery query parameter to the _dynamicUrl of the. In this part of the AEM Headless Developer Journey, learn how to use the REST API to access and update the content of your Content Fragments. SOLVED Headless integration with AEM. You might know that AEM offers a great interface for authors enabling them to create content by using predefined templates and web components. 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. AEM Headless APIs allow accessing AEM. Additionally, enable the GraphQL endpoint configurations that can be consumed by external applications to fetch headless content. To learn more about authenticating requests to AEM as a Cloud Service, review the token-based authentication tutorial. What you need is a way to target specific content, select what you need and return it to your app for further processing. The following configurations are examples. js App. The GraphiQL tool also enables users to persist or save queries to be used by client applications in a production setting. Prerequisites. Last update: 2023-08-16. api/Aem. Content Fragment Models Basics and Advanced features such as different Data types and respective usages. Use GraphQL schema provided by: use the drop-down list to select the required configuration. Overview. Content Fragments and Experience Fragments are different features within AEM:. ” Tutorial - Getting Started with AEM Headless and GraphQL. 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. AEM Headless clients operating in a production capacity typically interact with AEM Publish, which contains the approved, published content. Optional - How to create single page applications with AEM; Developer Portal (Additional Resources) Headless Content Architect Journey. The AEM Headless Client for JavaScript is used to execute the GraphQL persisted queries that power the app. ” Tutorial - Getting Started with AEM Headless and GraphQL. Clients interacting with AEM Author need to take special care, as AEM Author is secure by default, requiring authorization for all requests, and may also contain work in progress, or unapproved. Next, explore the power of AEM’s GraphQL API using the built-in GraphiQL Explorer. Deploying a SPA that interacts AEM in a headless manner involves hosting the SPA and making it accessible via a web browser. src/api/aemHeadlessClient. Example applications are a great way to explore the headless capabilities of Adobe Experience Manager (AEM). Adobe Experience Manager Assets HTTP API (Additional Resources) Content Fragments Support in AEM Assets HTTP API (Additional Resources) What’s Next. 5 the GraphiQL IDE tool must be manually installed. The last command simply renames the AEM project folder so it is clear it’s the AEM project, and not to be confused with Remote SPA_ While frontendModule="react" is specified, the ui. swift) contains a method makeRequest(. Confirm with Create. View the source code on GitHub. This article builds on those fundamentals so you understand how to access your existing headless content in AEM using the AEM GraphQL API. src/api/aemHeadlessClient. Open the Program containing the AEM as a Cloud Service environment to integrate set up the Service Credentials for. frontend project is not used for the Remote SPA use case. We’ll guide you through configuring your React app to connect to AEM Headless APIs using the AEM Headless SDK. Open the required model for Edit; use either the quick action, or select the model and then the action from the toolbar. See full list on experienceleague. 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. Path to Your First Experience Using AEM Headless {#path-to-first-experience} . In the future, AEM is planning to invest in the AEM GraphQL API. In the previous document of the AEM headless journey, How to Update Your Content via AEM Assets APIs you learned how to update your existing headless content in AEM via API and you should now: Understand. The execution flow of the Node. This involves structuring, and creating, your content for headless content delivery. The approach I am thinking of is, all fields on the SPA app can be rendered in XML/JSON via Web API. api/Aem. Front end developer has full control over the app. AEM Content Services allows for the same content abstractions used for authoring web pages in AEM Sites, to define the content and schemas of these. Previous page. The execution flow of the Node. js application demonstrates how to query content using AEM’s GraphQL APIs using persisted queries. The AEM Headless Client for JavaScript is used to execute the GraphQL persisted queries that power the app. Javadoc jar - the javadocs for the Java™ API jar; The AEM Headless SDK. The sample React app has three main parts: The src/api folder contains files used to make GraphQL queries to AEM. Lastly, the context. Last update: 2023-08-16. 5. Example server-to. Developers can use the JSON Preview in the Content Fragment editor to show all values of the current Content Fragment that can be returned using the GraphQL API. js (JavaScript) AEM Headless SDK for. x. The Create new GraphQL Endpoint dialog box opens. Server-to-server Node. The AEM Headless SDK is available for various platforms: AEM Headless SDK for client-side browsers (JavaScript) AEM Headless SDK for server-side/Node. This simple React app uses the AEM Headless SDK to query AEM Headless APIs for an Adventure content, and displays the web-optimized image using img element with srcset and picture element. In this chapter, we replace the Home view’s title, “Current Adventures”, which is hard-coded text in Home. 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. A Content author uses the AEM Author service to create, edit, and manage content. You also learn how you can create editable SPAs using AEM’s SPA Editor framework, and integrate external SPAs, enabling editing capabilities as required. js application run from the command line to update asset metadata on AEM as a Cloud Service using Assets HTTP API. This Next. AEM GraphQL API requests. Next, explore the power of AEM’s GraphQL API using the built-in GraphiQL Explorer. The HTTP GET requests from the headless app to AEM’s GraphQL APIs must be configured to interact with the correct AEM service, as. Deploying a SPA that interacts AEM in a headless manner involves hosting the SPA and making it accessible via a web browser. Navigate to the Software Distribution Portal > AEM as a Cloud Service. AEM provides two approaches for optimizing GraphQL queries: Hybrid filtering. Included in the WKND Mobile AEM Application Content Package below. Additional. Example applications are a great way to explore the headless capabilities of Adobe Experience Manager (AEM). Learn how to use the GraphQL API for headless delivery of Content Fragment content and. The srcset and sources use a custom setParams function to append the web-optimized delivery query parameter to the _dynamicUrl of the. Prerequisites. Tap or click Create. Select Create. Example server-to. The Story So Far. Understand how the source code for a Single Page Application (SPA) written in React can be integrated with an Adobe Experience Manager (AEM) Project. X) the GraphiQL Explorer (aka GraphiQL IDE) tool needs to be manually installed, follow instruction from here. In this part of the AEM Headless Developer Journey, learn how to deploy a headless application live. The tutorial explores token-based authentication using AEM Assets HTTP APIs but the same concepts and approaches are applicable to apps interacting with AEM Headless GraphQL APIs. View the source code on GitHub. Example applications are a great way to explore the headless capabilities of Adobe Experience Manager (AEM). 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. An end-to-end tutorial illustrating how to build-out and expose content using AEM Headless. Browse the following tutorials based on the technology used. The HTTP GET requests from the headless app to AEM’s GraphQL APIs must be configured to interact with the correct AEM service, as. The AEM Headless Client for Java is used to execute the GraphQL queries and map data to Java. This Android application demonstrates how to query content using the GraphQL APIs of AEM. . AEM Headless as a Cloud Service. From the AEM Start screen, navigate to Tools > General > GraphQL Query Editor. api/Aem. Cloud Service; AEM SDK; Video Series. By decoupling the CMS from the presentation layer, developers have the freedom to choose their preferred front-end frameworks and technologies. Next, explore the power of AEM’s GraphQL API using the built-in GraphiQL Explorer. How AEM headless CMS capabilities provide exceptional experiences? AEM is a headless CMS offering flexible and customizable architecture to provide developers and marketers with the tools to create. Download the latest GraphiQL Content Package v. AEM Headless CMS Developer Journey. Looking for a hands-on. Next, explore the power of AEM’s GraphQL API using the built-in GraphiQL Explorer. AEM Headless single-page app (SPA) deployments involve JavaScript-based applications built using frameworks such as React or Vue, that consume and interact with content in AEM in a headless manner. The React WKND App is used to explore how a personalized Target activity using Content. The developer performs most of the technical configurations to enable Content Architect and Content Authors to produce headless content. AEM Headless Web Component /JS deployments are pure JavaScript apps that run in a web browser, that consume and interact with content in AEM in a headless manner. In this part of the AEM Headless Developer Journey, learn how to use the REST API to access and update the content of your Content Fragments. In the previous document of the AEM. The following are examples of possible approaches for constructing URLs for AEM GraphQL API and image requests, for several popular headless frameworks and platforms. Select Create. Permission considerations for headless content. In the previous document of the AEM headless journey, How to Update Your Content via AEM Assets APIs you learned how to update your existing headless content in AEM via API and you should now: Understand. GraphQL persisted query Selecting the json response format for the multi-line field offers the most flexibility when working with rich text content. The Assets REST API is available on each out-of-the-box install of a recent Adobe Experience Manager as a Cloud Service version. The following are required to follow this quick setup: AEM as a Cloud Service Sandbox environment. js application demonstrates how to query content using AEM’s GraphQL APIs using persisted queries. This server-to-server application demonstrates how to query content using AEM’s GraphQL APIs using persisted queries and print it on terminal. This level of integration is the traditional headless model and allows your content authors to create content in AEM and deliver it heedlessly to any number of external services using GraphQL or to edit them from external services using the Assets API. Each guide builds on the previous, so it is recommended to explore them thoroughly and in order. Understand how the source code for a Single Page Application (SPA) written in React can be integrated with an Adobe Experience Manager (AEM) Project. Example applications are a great way to explore the headless capabilities of Adobe Experience Manager (AEM). In this video you will: Learn how to create and define a Content Fragment Model. Explore tutorials by API, framework and example applications. The following configurations are examples. The Story So Far. The following tools should be installed locally: JDK 11; Node. This end-to-end tutorial continues the basic tutorial that covered the fundamentals of Adobe Experience Manager (AEM) Headless and GraphQL. Command line parameters define: The AEM as a Cloud Service Author. The zip file is an AEM package that can be installed directly. But with the AEM Headless Developer Journey you are mentioning you’ll work with both solutions so I think at the end of the journey you can see the pro’s and con’s from both solutions. Questions. js) Remote SPAs with editable AEM content using AEM SPA Editor. If it is possible that I can render my app dynamic content in AEM using WebAPI. This setup establishes a reusable communication channel between your React app and AEM. View the source code on GitHub. Content can be viewed in-context within AEM. Understand how the AEM GraphQL API works. In this post, Adobe Experience Cloud introduces its Adobe Experience Manager Headless Extension for PWA Studio that enables developers to leverage headless architectures to build app-like experiences for their customers that. Headless is an example of decoupling your content from its presentation. Developer. AEM Headless Content Architect Journey Overview; Content Modeling for Headless with AEM - An Introduction; Learn the Content Modeling Basics for Headless with AEM; Learn about Creating. src/api/aemHeadlessClient. The React app should contain one instance of the <Page> component exported from @adobe/aem-react-editable-components. The AEM Headless Client for Java is used to execute the GraphQL queries and map data to Java. The AEM Headless Client for JavaScript is used to execute the GraphQL persisted queries that power the app. The Story So Far. Or in a more generic sense, decoupling the front end from the back end of your service stack. Content can be viewed in-context within AEM. com The developer develops the client that will consume content from AEM headless as the content authors are still creating the content. Adobe Experience Manager Sites lets marketers create content while allowing developers to focus on building and shipping code. Download the latest GraphiQL Content Package v. ) that prefixes AEM GraphQL APIs requests with the configured AEM scheme and host. ) that prefixes AEM GraphQL APIs requests with the configured AEM scheme and host. Improved Developer Experience Headless AEM also offers developers a more enjoyable and efficient development experience. X. This means you can realize headless delivery of structured. But with the AEM Headless Developer Journey you are mentioning you’ll work with both solutions so I think at the end of the journey you can see the pro’s and con’s from both solutions. The Story So Far. 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. This tutorial uses a simple Node. The AEM Headless Client for JavaScript is used to execute the GraphQL persisted queries that power the app. Developer. Headless AEM, or “decoupled” AEM, is Adobe Experience Manager’s approach to content delivery that separates the content from the presentation layer. Experience LeagueLearn how to use AEM’s Assets REST API to manage Content Fragments and the GraphQL API for headless delivery of Content Fragment content. In the last step, you fetch and display Headless. AEM Headless Content Architect Journey Overview; Content Modeling for Headless with AEM - An Introduction; Learn the Content Modeling Basics for Headless with AEM; Learn about Creating. The diagram above depicts this common deployment pattern. The srcset and sources use a custom setParams function to append the web-optimized delivery query parameter to the _dynamicUrl of the image, so change the. js application is as follows: The Node. From the AEM Start screen, navigate to Tools > General > GraphQL Query Editor. The two only interact through API calls. The GraphiQL Explorer tool enables developers to create, and test queries against content on the current AEM environment. . Rich text response with GraphQL API. This simple React app uses the AEM Headless SDK to query AEM Headless APIs for an Adventure content, and displays the web-optimized image using img element with srcset and picture element. ) that is curated by the. How to use AEM provided GraphQL Explorer and API endpoints. GraphQL persisted query Selecting the json response format for the multi-line field offers the most flexibility when working with rich text content. js application is as follows: The Node. Example applications are a great way to explore the headless capabilities of Adobe Experience Manager (AEM). js initializes and exports the AEM Headless Client used to communicate with AEM; src/api/usePersistedQueries. swift) contains a method makeRequest(. js application demonstrates how to query content using AEM’s GraphQL APIs using persisted queries. Headless AEM also offers developers a more enjoyable and efficient development experience. The multi-line text field is a data type of Content Fragments that enables authors to create rich text content. I should the request If anyone else calls AEM. AEM Local Development Access Tokens are used to accelerate the development of integrations with AEM as a Cloud Service that programmatically interacts with AEM Author or Publish services over HTTP. Some content is managed in AEM and some in an external system. 1 - Modeling Basics; 2 - Advanced Modeling; 3 - Creating GraphQL Queries; 4 - Content Fragment Variations; 5 - GraphQL Endpoints; 6 - Author and Publish Architecture; 7 - GraphQL Persisted. Each environment contains different personas and with. @adobe/aem-spa-component-mapping: provides the API that map AEM content to SPA components. Understand how the Content Fragment Model. Key Concepts. The Single-line text field is another data type of Content Fragments. What are GraphQL and Assets REST APIs? Now that you have created some content fragments, you can use AEM’s APIs to deliver them headlessly. This tutorial builds upon the WKND GraphQL App , a React app that consumes AEM Content Fragment content over AEM’s GraphQL APIs, however does not provide any in. 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 framework. Logical. The Story So Far {#story-so-far} . The advanced tutorial illustrates in-depth aspects of working with Content Fragment Models, Content Fragments, and the AEM GraphQL persisted. This end-to-end tutorial continues the basic tutorial that covered the fundamentals of Adobe Experience Manager (AEM) Headless and GraphQL. js application run from the command line to update asset metadata on AEM as a Cloud Service using Assets HTTP API. Prerequisites. View the source code on GitHub. Log in to AEM Author service as an Administrator. The AEM Headless SDK is available for various platforms: AEM Headless SDK for client-side browsers (JavaScript) AEM Headless SDK for server-side/Node. After completing the above enhancements the WKND App looks like below and browser’s developer tools shows adventure-details-by-slug persisted query call. With these operations the API lets you operate Adobe Experience Manager as a Cloud Service as a headless CMS (Content Management System) by providing. Dive into the details of the AEM. Operations User GuideAEM 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. Once headless content has been translated,. 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. This React application demonstrates how to query content using AEM’s GraphQL APIs using persisted queries. The following are required to follow this quick setup: AEM as a Cloud Service Sandbox environment. x. AEM Headless APIs allow accessing AEM content from any client app. Learn more. The AEM Headless SDK is available for various platforms: AEM Headless SDK for client-side browsers (JavaScript) AEM Headless SDK for server-side/Node. This end-to-end tutorial continues the basic tutorial that covered the fundamentals of Adobe Experience Manager (AEM) Headless and GraphQL. View the source code on GitHub. Developers can use the JSON Preview in the Content Fragment editor to show all values of the current Content Fragment that can be returned using the GraphQL API. @adobe/aem-spa-page-model-manager: provides the API for retrieving content from AEM. This is the first part of a series of the new headless architecture for Adobe Experience Manager. Understand how Content Fragments are supported in this API. The AEM Headless Client for JavaScript is used to execute the GraphQL persisted queries that power the app. This React. The advanced tutorial illustrates in-depth aspects of working with Content Fragment Models, Content Fragments, and the AEM GraphQL persisted queries, including using the. AEM 6.