supports headless CMS scenarios where external client applications render experiences using content managed in AEM. This is the first part of a series of the new headless architecture for Adobe Experience Manager. The AEM SDK. AEM exposes a variety of HTTP endpoints that can be interacted with in a headless manner, from GraphQL, AEM Content Services to Assets HTTP API. Learn how to connect AEM to a translation service. js app uses AEM GraphQL persisted queries to query adventure data. The ability to provide actual omnichannel experiences is therefore at your disposal, giving you the most. The application uses two persisted queries: wknd/adventures-all persisted query, which returns all adventures in AEM with an abridged set of properties. Adobe Commerce is fully headless with a decoupled architecture that provides all commerce services and data through a GraphQL API layer. 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 Content author uses the AEM Author service to create, edit, and manage content. All 3rd party applications can consume this data. Developing. Generally you work with the content architect to define this. AEM 6. Tap the ellipsis next to the environment in the Environments section, and select Developer Console. An end-to-end tutorial illustrating advanced concepts of Adobe Experience Manager (AEM) GraphQL APIs. js app uses AEM GraphQL persisted queries to query adventure data. These engagements will span the customer lifecycle, from. In the previous document of the AEM headless journey, Path to Your First Experience Using AEM Headless, you then learned the steps needed to implement your first project. Headless and AEM; Headless Journeys. Create your first React Single Page Application (SPA) that is editable in Adobe Experience Manager AEM with the WKND SPA. 1 - Modeling Basics; 2 - Advanced Modeling; 3 - Creating GraphQL Queries; 4 - Content Fragment Variations; 5 -. Before calling any method initialize the instance with GraphQL endpoint, GraphQL. 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. Join Host Danny Gordon and guests Amol Anand, Sachin Mali, and Sean St. The creation of a Content Fragment is presented as a wizard in two steps. The information within these dialogues is used to dynamically add content to components, enhancing the versatility of AEM-driven applications. Session SchedulingDate Speakers Build your first React app with Headless Experience Manager 9th November, 2022 | 10:00-10:45 PST OR 18:00-18:45 UTC OR 19:00-19:45 CET Stephan R. FTS - Forest Technology Systems, Victoria, British Columbia. This example application, using Next. AEM must know where the remotely rendered content can be retrieved. react project directory. For publishing from AEM Sites using Edge Delivery Services, click here. Let’s take a look to see how content fragment models and content fragments can help you with your AEM sites and headless use cases. This approach enables the CMS to live up to the promise of managing content in place and publishing anywhere. 924. . How to organize and AEM Headless project. Headless architecture is the technical separation of the head from the rest of the commerce application. Universal Editor Introduction. Rich text with AEM Headless. This means that instead of being limited to web publishing like a traditional CMS, content can be pushed to any end experience like a mobile app, SPA, or voice device. The use of Android is largely unimportant, and the consuming mobile 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. Content Models are structured representation of content. 5 Forms; Get Started using starter kit. Using the GraphQL API in AEM enables the efficient delivery of Content Fragments. Next, navigate to AEM to verify the updates and allow the OpenWeather component to be added to the SPA. But in Headless AEM , you create the content in AEM either using CF or a Template to expose the content as an API. js application is as follows: The Node. Headless implementations enable delivery of experiences across platforms and channels at scale. js. Headless CMS in AEM 6. An AEM project is required to setup-supporting configuration and content requirements to allow AEM SPA Editor to author a Remote SPA. Head:-Head is known as frontend and headless means the frontend is missing. Rich text with AEM Headless. They can also be used together with Multi-Site Management to. Single page applications (SPAs) can offer compelling experiences for website users. Tap in the Integrations tab. json extension. GraphQL API View more on this topic. Following AEM Headless best practices, the React application uses AEM GraphQL persisted queries to query adventure data. 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 configured AEM service’s host/domain is then used to construct the AEM GraphQL API URLs and Image URLs. 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. AEM Headless Client for Node. 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 ImageRef type has four URL options for content references: _path is the referenced path in AEM. The Content author and other. A detailed breakdown of the most common Adobe Experience Manager Sites implementations. Provide a Model Title, Tags, and Description. AEM Forms as a Cloud Service offers a user-friendly editor to create Headless Adaptive Forms. Take control of digital. The application uses two persisted queries: wknd/adventures-all persisted query, which returns all adventures in AEM with an abridged set of properties. The application uses two persisted queries: wknd/adventures-all persisted query, which returns all adventures in AEM with an abridged set of properties. Created for: Intermediate. Following AEM Headless best practices, the React application uses AEM GraphQL persisted queries to query adventure data. In this model, content is created in AEM, but styling it, presenting it, and delivering it all happen on another platform. The AEM Headless SDK is available for various platforms: AEM Headless SDK for client-side browsers (JavaScript) AEM Headless SDK for server-side/Node. Clients can send an HTTP GET request with the query name to execute it. The ImageRef type has four URL options for content references: _path is the referenced path in AEM. 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. Previous page. AEM Headless Content Author Journey. AEM as a Cloud Service is made up of high-level solutions such as AEM Sites, AEM Assets, and AEM Forms. Created for: Developer. Following AEM Headless best practices, the application uses AEM GraphQL persisted queries to query adventure data. When authoring pages, the components allow the authors to edit and configure the content. AEM 6. 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. Right now there is full support provided for React apps through SDK, however. Understand how it can help content authors deliver exceptional experiences, increase their content velocity, and how. An end-to-end tutorial illustrating how to build-out and expose content using AEM Headless. Headless CMS W ith a headless CMS, content is created independently of the final presentation layer. Learn how to use Content Fragments in Adobe Experience Manager (AEM) as a Cloud Service with the AEM GraphQL API for headless content delivery. adobe. This persisted query drives the initial view’s adventure list. The multi-line text field is a data type of Content Fragments that enables authors to create rich text content. 10. Developer. Following AEM Headless best practices, the Next. The configured AEM service’s host/domain is then used to construct the AEM GraphQL API URLs and Image URLs. This method can then be consumed by your own applications. AEM's headless CMS features allow you to employ many technologies to provide content across all channels. A detailed breakdown of the most common Adobe Experience Manager Sites implementations. AEM Headless Client for JavaScript Installation Usage Create AEMHeadless client Use AEMHeadless client Promise syntax: Within async/await: Pagination: Authorization API Reference Contributing LicensingAEM GraphQL API provides a powerful query language to expose data of Content Fragments to JavaScript clients in Headless CMS implementations. The preview experience links the AEM Author’s Content Fragment editor with your custom app (addressable via HTTP), allowing for a deep link into the app that renders the Content Fragment being previewed. This class provides methods to call AEM GraphQL APIs. Explore this guided journey through the powerful and flexible headless features of AEM to prepare for your first headless project. Since the SPA renders the component, no HTL script is needed. Navigate to Tools -> Assets -> Content Fragment Models. The application uses two persisted queries: wknd/adventures-all persisted query, which returns all adventures in AEM with an abridged set of properties. Prerequisites. X) the GraphiQL Explorer (aka GraphiQL IDE) tool needs to be manually installed, follow instruction from here. The new architecture supporting AEM as a Cloud Service involves some key changes to the overall developer experience. Here, the AEM will act as a mere repository, exposing content as a service in REST/ GraphQL endpoints. The AEM Headless quick setup gets you hands-on with AEM Headless using content from the WKND Site sample project, and a sample React App (a SPA) that consumes the content over AEM Headless GraphQL APIs. First select which model you wish to use to create your content fragment and tap or click Next. Tutorials by framework. Headless Developer Journey. Headless-cms-in-aem Headless CMS in AEM 6. AEM Rockstar Headless. You’ll learn how to format and display the data in an appealing manner. Make all your assets easy to find and use. This document. AEM’s GraphQL queries can be written to provide URLs to images based on where the image is referenced from. Using a REST API introduce challenges: Design Model Advantages Disadvantages; AEM is used as a headless CMS without using the SPA Editor SDK framework. html extension for . These services are licensed individually, but can be used in collaboration. Following AEM Headless best practices, the application uses AEM GraphQL persisted queries to query adventure data. This article explores the concept of using a headless CMS in AEM and how it can enhance content management and delivery. How to create. However headful versus headless need not be a binary choice in AEM. This chapter walks you through the steps to integrate the persisted queries with the WKND client application (aka WKND App) using HTTP GET requests within existing React components. Headless content management is a key development for today’s web design that decouples the frontend, client-side applications from the backend, content management system. The following are required to follow this quick setup: AEM as a Cloud Service Sandbox environment. This comes out of the box as part of. Headless implementation forgoes page and component management, as is. Using this path you (or your app) can: receive the responses (to your GraphQL queries). JavaScript Object Notation ( JSON ) is strictly a text-based format used to represent structured data and is based on JavaScript object syntax. 0 versions enable the GraphQL runtime platform to expose the Content Fragments through GraphQL API. This persisted query drives the initial view’s adventure list. Tap the Title component, and tap the wrench icon to edit the Title component. Connectors User Guide: Learn how to integrate Connectors into Experience Manager as. In, some versions of AEM (6. 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. Learn how to deep link to other Content Fragments within a. Authorized requests to AEM GraphQL APIs they typically occur in the context of server-to-server apps, since other app types, such as single-page apps, mobile, or Web Components, typically do use authorization as it is difficult to secure the credentials . At the beginning of the AEM Headless Content Architect Journey the Introduction covered the basic concepts and terminology relevant to modeling content for headless. Content authors cannot use AEM's content authoring experience. 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. This journey lays out the requirements, steps, and approach to translate headless content in AEM. 1. Understand how it can help content authors deliver exceptional experiences, increase their content velocity, and how provides a state-of-the-art. One needs to fetch The Form JSON from aem using the headless APIs. AEM Headless tutorials - If you prefer to learn by doing and have existing knowledge of AEM, take our hands-on tutorials organized by API and framework, that explore creating and using applications built on AEM Headless. Learn about the architecture of AEM Forms Headless Adaptive Forms and how it can help you quickly build forms for various platforms. Learn about the concepts and. Headless Journeys are designed for varying personas, laying out the requirements, steps, and approach to implementing headless solutions from different. AEM: GraphQL API. Developer. Before calling any method initialize the instance with GraphQL endpoint, GraphQL serviceURL and auth if needed Typedefs Model: object . When authorizing requests to AEM as a Cloud Service, use. 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. Developer. The two only interact through API calls. How to create headless content in AEM. Last update: 2023-06-27. This is where you create the logic to determine your audiences. Create and manage engaging content at scale with ease. AEM’s GraphQL APIs for Content Fragments. A well-defined content structure is key to the success of AEM headless implementation. A headless CMS is 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. The focus lies on using AEM to deliver and manage (un. 0+ version supports GraphQL API to expose the Content Fragment to enable the headless content experience. 5 or later; AEM WCM Core Components 2. Last update: 2023-10-04. ) that is curated by the. The GraphiQL tool enables developers to create and test queries against content on the current AEM environment. 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. The full code can be found on GitHub. In the Create Site wizard, select Import at the top of the left column. react $ mvn clean install -PautoInstallSinglePackage Update the Template Policy. 3, Adobe has fully delivered its content-as-a. env files, stored in the root of the project to define build-specific values. AEM components are used to hold, format, and render the content made available on your webpages. AEM is a cloud-native solution, providing automated product updates to ensure teams always have the latest features and enhancements. It is a go-to. Persisted queries are GraphQL queries that are created and stored on the Adobe Experience Manager (AEM) server. In this chapter of Advanced concepts of Adobe Experience Manager (AEM) Headless, learn how to edit a Content Fragment Model by adding tab placeholders, date and time, JSON objects, fragment references, and content references. From the AEM Start screen, navigate to Tools > General > GraphQL Query Editor. 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. Cloud Service; AEM SDK; Video Series. React environment file React uses custom environment files , or . Regardless of which model you choose to implement for SSR, you must specify to AEM how to access this remote rendering service. Headless AEM addresses these limitations by embracing a decoupled and API-driven approach, empowering organizations to adapt quickly to changing customer needs and technological advancements. js, demonstrates how to query content using AEM’s GraphQL APIs with persisted queries. Using the AEM JSON exporter, you can deliver the contents of any AEM page in JSON data model format. Tap or click the folder you created previously. The most common deployment pattern with AEM headless applications is to have the production version of the application connect to an AEM Publish service. React environment file React uses custom environment files , or . Transcript. head-full implementation is another layer of complexity. js application is invoked from the command line. Prior to starting this tutorial ensure the following AEM instances are installed and running on your local machine:A well-defined content structure is key to the success of AEM headless implementation. Content Fragments used in AEM Headless content modeling, often reference image assets intended for display in the headless experience. We’ll guide you through configuring your React app to connect to AEM Headless APIs using the AEM Headless SDK. Headless eCommerce AEM with Magento deployment models. Often, these headless consumers may need to authenticate to AEM in order to access protected content or actions. A language root folder is a folder with an ISO language code as its name such as EN or FR. While client-side GraphQL queries can also be executed using HTTP POST requests, which cannot be cached, persisted. js implements custom React hooks. By utilizing the AEM Headless SDK, you can easily query and fetch Content Fragment data using GraphQL. Building a React JS app in a pure Headless scenario. Rich text with AEM Headless. From the AEM Start screen, navigate to Tools > General > GraphQL Query Editor. 5 and Headless. Flood Resilience and Planning. The multi-line text field is a data type of Content Fragments that enables authors to create rich text content. Build a React JS app using GraphQL in a pure headless scenario. This end-to-end tutorial continues the basic tutorial that covered the fundamentals of Adobe Experience Manager (AEM) Headless and GraphQL. Enable Headless Adaptive Forms on AEM 6. The React app should contain one instance of the <Page> component exported from @adobe/aem-react-editable-components. AEM HEADLESS SDK API Reference Classes AEMHeadless . 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. ; Know the prerequisites for using AEM's headless features. AEM offers the flexibility to exploit the advantages of both models in. Topics: Content Fragments View more on this topic. Developer. js app uses AEM GraphQL persisted queries to query adventure data. This React application demonstrates how to query content using AEM’s GraphQL APIs using persisted queries. AEM was being used in a headful manner but AEM imposed a lot of restrictions when we had to develop Applications on top of AEM; So we are going to use AEM in a headless manner and bring in all the content in content fragments so that those content fragments can be rendered on different portals (some use cases need more than. supports headless CMS scenarios where external client applications render experiences using content managed in AEM. The main idea behind a headless CMS is to decouple the frontend from the backend and. js in AEM, I need a server other than AEM at this time. Chapter 2 of the AEM Headless tutorial covers enabling and defining Content Fragment Models used to define a normalized data structure and authoring interface for creating Events. The headless CMS extension for AEM was introduced with version 6. Log into AEM and from the main menu select Tools -> Assets -> Content Fragment Models. Content Fragments, independent of layout, can be used directly in AEM Sites with Core Components or can be delivered in a headless manner to downstream channels. AEM Component Development: This stage involves creating dialogs in XML and developing client libraries. AEM has multiple options for defining headless endpoints and delivering its content as JSON. The new architecture supporting AEM as a Cloud Service involves some key changes to the overall developer experience. The application uses two persisted queries: wknd/adventures-all persisted query, which returns all adventures in AEM with an abridged set of properties. - AEM Headless CMS integrates easily with other tools and platforms giving exceptional customer experiences throughout the execution cycle. Explore the potential of headless CMS. During the creation of the launch the production web site can continue to evolve and change day to day as it normally would. The AEM Headless SDK is available for various platforms: AEM Headless SDK for client-side browsers (JavaScript) AEM Headless SDK for server-side/Node. 5. 5 is a flexible tool for the headless implementation model by offering three powerful services: Content Models. Open the react-starter-kit-aem-headless-forms directory in a code editor and navigate to eact-starter-kit-aem-headless-formssrccomponents. Bootstrap the SPA. How to create headless content in AEM. X. Example applications are a great way to explore the headless capabilities of Adobe Experience Manager (AEM). User. Following AEM Headless best practices, the iOS application uses AEM GraphQL persisted queries to query adventure data. AEM as a Cloud Service and AEM 6. The AEM Headless client, provided by the AEM Headless Client for JavaScript, must be initialized with the AEM Service host it connects to. Content Translation allows you to create an initial. The diagram above depicts this common deployment pattern. An individual journey is defined for a specific persona or audience, but also defines additional personas with which the reader interacts. The React app should contain one. Last update: 2023-10-04. Looking for a hands-on tutorial? Check out Getting Started with AEM Headless and GraphQL end-to-end tutorial illustrating how to build-out and expose content using AEM’s GraphQL APIs and consumed by an external app, in a headless CMS scenario. Tutorial Set up. Tap or click Create. The AEM Headless client, provided by the AEM Headless Client for JavaScript, must be initialized with the AEM Service host it connects to. Adobe Experience Manager Sites Features Headless CMS Developers and business users have the freedom to create and deliver content using headless or headful models out of. HTML is rendered on the server Static HTML is then cached and delivered The management of. Log into AEM as a Cloud Service and from the main menu select Tools > General > Configuration Browser. 5 is a flexible tool for the headless implementation model by offering three powerful services: Content Models. 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. Adobe Experience Manager supports a headless approach, freeing it from being bound to its historical Java-based web development. 0 or later. Headless implementations enable delivery of experiences across platforms and channels at scale. This journey is designed for the translation specialist persona, often referred to as the Translation Project Manager or TPM. Headless AEM offers a host of benefits that can revolutionize the way businesses approach content management. Learn the Content Modeling Basics for Headless with AEM; Learn about Creating Content Fragment Models in AEM; Headless Translation Journey. You’ll learn how to format and display the data in an appealing manner. You will also learn how to use out of the box AEM React Core. Run the following command to build and deploy the entire project to AEM: $ mvn clean install -PautoInstallSinglePackage. 5 and Headless. You really don't invest much in the FE design in AEM , as the content is delivered only as JSON to be consumed by your services. A language root folder is a folder with an ISO language code as its name such as EN or FR. Included in the WKND Mobile AEM Application Content Package below. How to organize and AEM Headless project. The React WKND App is used to explore how a personalized Target. Set up headless content delivery and management in AEM by Jeremy Lanssiers Overview We set up headless content delivery and headless content management by using AEM’s GraphQL to deliver and Assets API to manage content (via Content Fragments). We’ll cover best practices for handling and rendering Content Fragment data in React. Following AEM Headless best practices, the application uses AEM GraphQL persisted queries to query adventure data. AEM has multiple options for defining headless endpoints and delivering its content as JSON. AEM’s SPA Editor provides authors the ability to edit content for a Single Page Application or SPA. Scenario 2: Hybrid headless commerce AEM. Or in a more generic sense, decoupling the front end from the back end of your service stack. References to other content, such as images or other Content Fragments can be dynamically inserted in-line within the flow of the text. For publishing from AEM Sites using Edge Delivery Services, click here. It is helpful for scalability, usability, and permission management of your content. AEM understands every business's need for headless content management while building a foundation for future growth. In this part of the AEM Headless Developer Journey, learn about headless technology and why you would use it. 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 response of a GET request can be cached at the Dispatcher and Content Delivery Network (CDN) layers, ultimately improving the performance of the. Developer. The React App in this repository is used as part of the tutorial. The AEM Headless quick setup gets you hands-on with AEM Headless using content from the WKND Site sample project, and a sample React App (a SPA) that consumes the content over AEM Headless GraphQL APIs. Now free for 30 days. The focus lies on using AEM to deliver and manage (un)structured data. AEM Headless is a CMS solution from Experience Manager that allows structured content (Content Fragments) in AEM to be consumed by any app over. The Content author and other. An end-to-end tutorial illustrating how to build-out and expose content using AEM Headless. Multiple requests can be made to collect as many results as required. supports headless CMS scenarios where external client applications render experiences using. Create the Sling Model. Use GraphQL schema provided by: use the drop-down list to select the required configuration. Tutorial - Getting Started with AEM Headless and GraphQL. 1. AEM Headless Developer Portal; Overview; Quick setup. Provide a Title and a Name for your configuration. Then Getting Started with AEM Headless as a Cloud Service described AEM Headless in the context of your own project. Following AEM Headless best practices, the Next. Tap Create new technical account button. Developer. ; Be aware of AEM's headless integration. By integrating with personalization platforms or. 5. The application uses two persisted queries: wknd/adventures-all persisted query, which returns all adventures in AEM with an abridged set of properties. Headless is an example of decoupling your content from its presentation. Tutorials by framework. Content Models serve as a basis for Content Fragments. AEM has been adding support for headless delivery for a while, starting with simply swapping the . The AEM Headless quick setup gets you hands-on with AEM Headless using content from the WKND Site sample project, and a React App that consumes the content over AEM Headless GraphQL APIs. TIP. Let’s start by looking at some existing models. This is done via the RemoteContentRenderer - Configuration Factory OSGi service. 3 and has improved since then, it mainly consists of the following components: 1. json to a published resource. This CMS approach helps you scale efficiently to. Wrap the React app with an initialized ModelManager, and render the React app. Launches in AEM Sites provide a way to create, author, and review web site content for future release. The AEM Headless Client for JavaScript is used to execute the GraphQL persisted queries that power the app. Next. AEM’s GraphQL queries can be written to provide URLs to images based on where the image is referenced from. These services are licensed individually, but can be used in collaboration. Currently t he GraphQL feature is enabled by default only on the AEM SDK from 2021-02-04 or newer on AEM as Cloud Service. An end-to-end tutorial illustrating how to build-out and expose content using AEM Headless. Learn how the Universal Editor enables what-you-see-is-what-you-get (WYSIWYG) editing of any headless and headful experience. By. g es, to make it is accessible and useable across global customers. React environment file React uses custom environment files , or . Content Models serve as a basis for Content. A headless CMS is therefore responsible for the (backend) content management services, together with the mechanisms allowing the (frontend) applications to access that content. The Story So Far. Learn how multiple views in the SPA are supported using AEM Pages and the SPA Editor SDK. In this video you will: Learn how to create and define a Content Fragment Model. This persisted query drives the initial view’s adventure list. Headful and Headless in AEM; Headless Experience Management. env files, stored in the root of the project to define build-specific values. This CMS approach helps you scale efficiently to. react. It is the main tool that you must develop and test your headless application before going live. Unlike the traditional AEM solutions, headless does it without the presentation layer. Select Create at the top-right of the screen and from the drop-down menu select Site from template. Release Notes. This approach enables the CMS to live up to the promise of managing content in place and publishing anywhere. Following AEM Headless best practices, the iOS application uses AEM GraphQL persisted queries to query adventure data. Select Create. Right now there is full support provided for React apps through SDK, however. Merging CF Models objects/requests to make single API. Let’s take a look to see how content fragment models and content fragments can help you with your AEM sites and headless use cases. They allow you to prepare content ready for use in multiple locations/over multiple channels, ideal for headless delivery. AEM exposes a variety of HTTP endpoints that can be interacted with in a headless manner, from GraphQL, AEM Content Services to Assets HTTP API.