Body is where the content is stored and head is where it is presented. It makes content generation, administration, and editing easier for big content teams with daily deadlines. 1. On this page. The TagID is added to the content node’s cq:tags property and resolves to a node of type cq:Tag. That said, it is way easier with Franklin to achieve these results because they are assured by how the platform builds and delivers your content. In this context, extending AEM as a Cloud Service, an overlay means to take the predefined. This document helps you understand headless content delivery, how AEM supports headless, and how. With headless CMSs, the stored content is made available to developers through APIs. In the future, AEM is planning to invest in the AEM GraphQL API. A headless CMS allows you to manage content in one place and be able to deploy that content on any digital channel you choose. 4005. 2. Headless Journeys are designed for varying personas, laying out the requirements, steps, and approach to implementing headless solutions from different. KOR for deploying Strapi. Check both AEM and Sling plugins. Adobe Sensei powers you to automatically convert all your legacy PDF forms and traditional input fields to digital, mobile-responsive, adaptive forms. An article will be released soon on our blog, stay. A headless CMS is a content management system (like a database for your content). By utilizing the AEM Headless SDK, you can easily query and fetch Content Fragment data using GraphQL. CMS consist of Head and Body. From improving business strategies to growing revenue, let’s have a look at a few business advantages from marketing aspects: Conclusion. Getting Started with AEM Headless. Sanity is the fully customizable, headless CMS. 5 The headless CMS extension for AEM was introduced with version 6. Discover how:Headless CMS is also particularly suitable for websites designed using the Jamstack model where JavaScript, APIs, and Markup work together to make web development easier and user experiences better. This allows to deliver data to 3rd party clients other than AEM. Digital asset management. AEM's headless features provide the flexibility needed for delivering content independently from its presentation, allowing for dynamic and responsive user experiences. 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). Organizations deliver content like images, articles, blogs, and videos to their customers through their applications, social media, and websites. Search Results. This involves structuring, and creating, your content for headless content delivery. This guide provides important information about the latest release of Experience Manager as a Cloud Service, including what’s new deprecated and removed features,. Looking for a hands-on. 5, AEM Forms author can leverage the. Having a multi-tenant CMS with headless architecture is now a necessity. To wrap up, the Visual SPA Editor is available now in Magnolia 6. What this really means is that a headless CMS allows you to manage content in one. Next. Monolithic vs decoupled vs headless architectures. Headless CMS Explained in 2 Minutes. Tap or click the folder you created previously. Analytics &. Displaying the content is left to other, more specialized applications. Strapi allows creating, managing, and distributing a content-rich. See Wikipedia. Headless offers the most control over how and where your content appears. cfg. Instead, a headless CMS acts as a content-only data source and delivers content as data outputs, usually via the JSON open standard file format and data interchange format. Navigate to Tools, General, then select GraphQL. In a nutshell, headless delivery takes away the page rendering responsibility from the CMS. , a backend-only content management system allows you to manage and re-use digital content from a single repository and publish it on different applications. The power of AEM allows it to deliver content either headlessly, full-stack, or in both. Adobe Experience Manager Assets is a DAM that gives you automation and tools to rapidly source, adapt, and deliver your assets across audiences and channels so you can spend less time searching for and adjusting content. A headless CMS is a back-end only content management system (CMS) typically built as an API-first content repository. Experience League. Content Fragments: Allows the user to add and. This document gives a detailed overview of the various parts that make up AEM and is intended as a technical appendix for a full-stack AEM developer. What is Headless CMS . For example, to grant access to the. A headless CMS is a back-end-only content management system that allows you to create and store the content in the backend and deliver your content as data over an API to wherever you choose. Courses. The headless approach allows developers to provide content as a service, abbreviated as CaaS, which simply means that content storage and delivery are handled by separate software. in our case it will be AEM but there is no head, meaning we can decide the head on our own. Looking for a hands-on. For the headless approach, all screens are connected with the Magento CMS. It is a traditional, monolithic CMS with a content-as-a-service (CaaS) API. Consequently, a SaaS CMS is a centrally hosted CMS application that you can access through the web on any device and in any place. 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. Headless implementations enable delivery of experiences across platforms and channels at scale. In this session, we will be joined by Thomas Reid from Australian retailer Big W to discuss how Big W is enhancing their digital customer experience using AEM Headless. 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. Instead, it provides an API for developers to access and retrieve content, which can be displayed on any device or platform. Headless Architecture. Headless CMS werden deshalb hauptsächlich in Multichannel-Umgebungen eingesetzt. 3, Adobe has fully delivered its content-as-a. For you devs we've created a minimal demo project and a tutorial. And you can learn how the whole thing works in about an hour and a half. As long as the new technology can consume JSON, you’re good to go. A well-defined content structure is key to the success of AEM headless implementation. Each guide builds on the previous, so it is recommended to explore them thoroughly and in order. AWS. 2 days ago · Headless CMS (content management system) in recent times has come to trump the traditional CMS when juxtaposed as content management systems. AEM as a Cloud Service and AEM 6. 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. Tap or click Create. Organizations deliver content like images, articles,. Below we will compare these two types of solutions according to 5 parameters. Tap or click Create. This allows your development team to create a custom front-end. This is becoming more popular, and some of the renowned sites developing headless sites at the moment are adopting these. In a headless model, the content is managed in the AEM repository, but delivered via APIs such as REST and GraphQL to another system to render the content. Here, the AEM will act as a mere repository, exposing content as a service in REST/ GraphQL endpoints. AEM is a headless CMS that enables developers to easily manage and publish content across multiple channels. With a headless CMS, you will be able to reuse resources and content across multiple sites and web-based applications like single-page applications. Headless CMS. AEM as. Move faster with powerful developer tools. Learn about Headless CMS. It supports both traditional and headless CMS operations. e. Once we have the Content Fragment data, we’ll integrate it into your React app. Unlike the traditional AEM solutions, headless does it without the presentation layer. Learn why more and more companies are switching to headless CMS. In terms of authoring Content Fragments in AEM this means that:AEM 6. The open-ended front end provides businesses with greater flexibility, allowing them to adjust their distribution strategy as new opportunities or goals arise. 5. Security. Headless CMS disconnects the back end (aka the “body”) of the platform where content is created, managed, and stored from the front-end (aka the “head”) of the platform where content is formatted, designed, and distributed. includeChildren (boolean value, default: false). Content Models serve as a basis for Content Fragments. Headless CMS W ith a headless CMS, content is created independently of the final presentation layer. 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). Using a headless CMS, which stores content in a cloud repository as opposed to a server, will leverage less bandwidth, save resources, and reduce. Instead, you control the presentation completely with your own code in any programming language. It is not intended as a getting-started guide. Before we get too technical, let’s start with what this means in context of brand experience. the content repository). The AEM Headless Client for JavaScript is used to execute the GraphQL persisted queries that power the app. Because headless CMS is essentially an API, the content saved in it is easier to handle and integrate with other systems than information kept in a traditional CMS. 3 and has improved since then, it mainly consists of the following components: Content Services: Expose user defined content through an API in JSON format. A headless CMS focuses only on creating content and providing a way to retrieve it. Now, the focus isn’t about presenting content in a simple and user-friendly way – it’s about presenting data, when and where you want. If you are an AEM or Sitecore. Cockpit is a free, open-source and self-hosted headless CMS that describes itself as a “content provider” and “not a website builder. Traditional WordPress, Sitecore, and Drupal monoliths are built to serve. Understand Headless in AEM; Learn about CMS Headless Development; Getting Started with AEM Headless as a Cloud Service. AEM Overview. Recommended courses. cors. Thus, uploading content can be done quickly, with one unified branding message. We have written about headless CMS and how it is better than traditional CMS previously. A headless CMS completely separates the backend (creation and storage) from the frontend (design and deployment). AEM Headless Content Author Journey - Overview; Authoring for Headless with AEM - An Introduction; Authoring Basics for Headless with AEM; Learn about using references in Content Fragments; Learn about defining Metadata and Tagging for Content Fragments; Implementing. 8. AEM as a Cloud Service and AEM 6. 10. Is AEM Headless CMS? Yes! AEM, or Adobe Experience Manager, is not just a traditional Content Management System (CMS); it's also a robust headless CMS solution. In its place is a flexible API that can shoot data – be it a blog post or a customer profile – wherever you want. A Sitecore CMS headless allows us to deliver a rich experience on mobile apps and IoT devices quickly. 4. Headless CMS are not in direct competition with no-code tools. This article introduces the basic concepts of SPAs before leading the reader through a walkthrough of the SPA editor by using a simple SPA application to demonstrate basic content editing. At One Inside, our expertise relies on the implementation of the Adobe CMS, Adobe Experience Manager (AEM). What Is Adobe AEM? Adobe AEM is a powerful CMS used to create, edit, and manage digital content across various channels. What is a Headless CMS? A Headless CMS is a content management system that does not require a graphical interface. 5 billion by 2026. This decoupling means your content can be served into whatever head or heads you want. A headless approach allows the same content to be utilized by a wider number of channels. This means your content can reach a wide range of devices, in a wide range of formats and with a. Content-friendly. Headless CMS Developers and business users have the freedom to create and deliver content using headless or headful models out of the box, letting them structure and deliver content to any front-end framework. This involves structuring, and creating, your content for headless content delivery. AEM is used as a headless CMS without using the SPA Editor SDK framework. Unlocking the Value of AEM. Either (as AEM’s SPA Editor works) the CMS can publish integrated content to the SPA framework in context. With AEM, developers can create and manage content in a single place, and then publish it to multiple channels, including websites, mobile apps, and connected devices. The most common deployment pattern with AEM headless applications is to have the production version of the application connect to an AEM Publish service. 5. AEM's hybrid CMS approach has made it a popular choice among enterprises looking to transition to a headless architecture while still maintaining traditional content management capabilities. A headless CMS is a content management system where the frontend and backend are separated from each other. A modern content delivery API is key for efficiency and performance of Javascript-based frontend applications. AEM offers the flexibility to exploit the advantages of both models in. AEM does it for you by capturing user details such as location, relationship to available products, usage & search history, and much more data. The headless CMS has an API for the. With Contentstack and Adobe DAM, you can take your user's experience to the next level. Headless offers the most control over how and where your content appears. For the purposes of this getting started guide, we will only need to create one. As learned, a hybrid CMS clearly has benefits over traditional AEM and a headless CMS. It supports both traditional and headless CMS operations. Utilizing AEM as a hybrid CMS allows you to choose the. This document provides and overview of the different models and describes the levels of SPA integration. Body is where the content is stored and head is where it is presented. This journey provides you with all the information you need to develop. Get Started with AEM Headless Translation. And while headless architecture offers a great deal of flexibility in formats and display options, this can’t be achieved by focusing too much on the. What Makes AEM Headless CMS Special. 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. Its capabilities are not limited to publishing content but creating compelling product pages that form the very foundation on online shopping. 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. During the last few years, while some promoted a new publishing concept called ‘headless CMS’, Adobe introduced a few new tricks in AEM to fulfil the needs of the headless community, Content Fragments and Experience Fragments. ”. The AEM platform includes various open source elements like OSGi Application Runtime, Web Application Framework, which is Apache Sling. Ready-to-use templates and blocks of no-code builders significantly boost the process of bringing a website or app project to life. 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. App-Only —. 1. AEM as a Cloud Service GraphQL API used with Content Fragments is heavily based on the standard, open source GraphQL API. Get to know how to organize your headless content and how AEM’s translation tools work. Adobe Experience Manager (AEM) CMS is a versatile solution for businesses across verticals- digital commerce, manufacturing, healthcare, financial services, and so on. AEM: Headless vs. Your CMS is truly headless only if the content is completely separated from the context it is displayed in, that is, you should be able to change the destination of where the content goes, and have your front end determine where and how to layout the content. - AEM Headless CMS integrates easily with other tools and platforms giving exceptional customer experiences throughout the execution cycle. It’s 100% JavaScript, fully customizable, and developer-first. All content is stored and managed in a backend, and users can access it through a REST API. Here’s what you need to know about each. Headless CMSs are frontend agnostic and API-driven by design. Developer. This class provides methods to call AEM GraphQL APIs. Cockpit. The main strength of the AEM as a content management system comes from its decoupled architecture. AEM is designed to deliver exceptional user experience across platforms such as desktop, mobile, email, and social channels. Overview. Headless unlocks the full potential of shopping experiences by letting merchants quickly author and deliver app-like experiences across any touchpoint, including single-page and multi-page web apps, mobile apps, IoT devices, and VR and AR. Get to know how to organize your headless content and how AEM’s translation tools work. ” Tutorial - Getting Started with AEM Headless and GraphQL. This document. A human torso was discovered lying on a Queens beach by police,. Create Content Fragments based on the. 5 The headless CMS extension for AEM was introduced with version 6. AEM Headless CMS Developer Journey. Adobe Experience Manager (AEM) - Adobe's AEM combines traditional CMS capabilities with the flexibility of a headless approach. Due to this approach, a headless CMS does not. Salesforce CMS is a hybrid CMS, which means your teams can create content in a central location, and syndicate it to any digital touchpoint. Among numerous advantages as a headless ecommerce platform, Drupal offers: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 CMS exposes the data via one or more APIs, which the front-end systems interact with to retrieve the data when needed. the website) off the “body” (the back end, i. In this phase of the AEM as a Cloud Service Migration Journey, you familiarize yourself with AEM as a Cloud Service. Typically headless approach means an API approach, we are trying to give responsibility for each and individual component, also we are applying a common repository pattern. At the beginning of the AEM Headless Content Author Journey the Content Modeling Basics for Headless with AEM covered the basic concepts and terminology relevant to authoring for headless. According to marketing experts, the Adobe Experience Manager Headless Content Management System is the future of content delivery. AEM offers you a cloud-native, modern CMS, which is a combination of headless capabilities based on three main AEM headless CMS features that are: Content Fragments: Content fragments are code-free structured content created by authors using AEM Content Fragment Model Editor. Know the prerequisites for using AEM’s headless features. ” Tutorial - Getting Started with AEM Headless and GraphQL. This pattern can be used in any SPA and Widget approach but does make AEM more developer-focused. Adobe AEM stands out as an exceptionally popular CMS system, especially among enterprise users, thanks to its comprehensive functionalities and features. It is a query language API. An introduction to the headless features of Adobe Experience Manager, and how to author content for your project. Content authors cannot use AEM's content authoring experience. to gain points, level up, and earn exciting badges like the newPress Done to save the Workflow model. AEM Headless CMS – GraphQL by Mujafar Shaik Abstract Hello everyone, Today I came with an exciting topic, AEM Headless CMS with GraphQL. The frontend consumes this API data through components and renders the output on server (SSR). Hybrid. Tutorials. Using this path you (or your app) can: receive the responses (to your GraphQL queries). On Adobe headless CMS, modular content fragments can be easily reused across channels and devices and localized using Adobe Exchange’s translation capabilities. e. 10. At One Inside, our expertise relies on the implementation of the Adobe CMS, Adobe Experience Manager (AEM). Headless AEM is an architectural approach where the content management capabilities of Adobe Experience Manager are decoupled from the presentation layer. On the other hand, Headless CMS offers more performance, scalability, and flexibility by separating content production and storage from content delivery. In addition to offering robust tools to create, manage, and deliver traditional webpages in the full-stack fashion, AEM also offers the ability to author self-contained selections of content and serve them headlessly. The “head,” in the term “headless CMS” is where the content is presented. In a headless setup, the presentation system (the head) is decoupled from the content management (the tail). Content Fragment models define the data schema that is. IWD Agency: Us: [email protected] headless CMS approach is great for so many reasons, but it is a step backwards for the authoring experience. 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. impl. Cosmic is a Headless CMS meaning that the content API and presentation layer are decoupled which gives your team greater flexibility when it. 3. With Headless Adaptive Forms, you can streamline the process of. The CMS exposes the data as an API, and other applications can consume it in order to process and render it. This tutorial explores how AEM’s GraphQL APIs and headless capabilities can be used to power the experiences surfaced in an external app. (AEM) is a popular content management system that comes as part of the Adobe suite of products. Get to know how to organize your headless content and how AEM’s translation tools work. By making the switch to Contentstack, we’ll be able to provide creative, unique content experiences and operate with speed and flexibility for. 2: Authoring Basics for Headless with AEM: Learn about the concepts and mechanics of authoring content for your Headless CMS. If you are new to AEM and/or headless, AEM’s Headless Journeys are a great place to start to understand the theory and technology by way of a narrative to solve various business problems in a headless fashion. For headless, your content can be authored as Content Fragments. Headless implementations enable delivery of experiences across platforms and channels at scale. One such quick and easy way is to use our Delivery APIs in a Spring Boot web application deployed on Heroku. In this optional continuation of the AEM Headless Developer Journey, you learn how AEM can combine headless delivery with traditional full-stack CMS features. At the beginning, Learn About CMS Headless Development covered headless content delivery and why it should be used. Digital asset management. AEM's headless CMS features allow you to employ many technologies to provide content across all channels. Editable fixed components. When this content is ready, it is replicated to the publish instance. It is a content management system that does not have a pre-built front-end or template system. Using Adobe Experience Manager as your headless CMS within your digital content supply chain can allow your organization to run a more competitive content program and realize a better return on marketing efforts in multiple ways. As part of its headless architecture, AEM is API-driven. Last update: 2023-09-26. Using headless e-commerce allows you to separate the CMS from the e-commerce engine part. Click Add…. With the help of the AEM stack, we can implement this methodology. With Adobe Experience Manager (AEM), you can selectively access your Content Fragments, using the AEM GraphQL API, to return only the content that you need. The Story So Far. Manage GraphQL endpoints in AEM. These remote queries may require authenticated API access to secure headless content. Here you can specify: Name: name of the endpoint; you can enter any text. Select Create. In the previous document of the AEM headless journey, Getting Started with AEM Headless you learned the basic theory of what a headless CMS is and you should now: Understand the basics of AEM’s headless features. This provides you with maximum flexibility and capability to offer true omnichannel experiences. The headless approach in AEM has the following features and functionalities: Omnichannel delivery: Headless is preferred when the content is consumed through multiple channels. At Brightspot, we believe in front-end freedom of choice—to be able to. ; replicateAsParticipant (boolean value, default: false). Business moves faster when teams producing content have a platform that empowers them to collaborate, innovate, and. e. What is a headless CMS? Headless architecture offers a new way of presenting AEM content. 1 Answer. 3 and has improved since then, it mainly consists of the following components: 1. This allows businesses to adapt the customer experience across various touchpoints without impacting backend processes like inventory management and order fulfillment. It is the preferred choice for government agencies and content-heavy websites, like The Tonight Show with Jimmy Fallon or The White House. Persisted queries. 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. Be aware of AEM’s headless integration levels. A modern content delivery API is key for efficiency and performance of Javascript-based frontend applications. Pros and Cons of Using AEM as a Headless CMS. 252. Headless content management in AEM. Henceforth, AEM lets you deliver personalized content to every customer visiting. While having started its life as a classic monolithic CMS running on-premise, AEM has advanced a lot recently. 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. 4. The good news is that the leading CMS on the market, Adobe Experience Manager (AEM), works perfectly as a Headless CMS. Now that you have read the article AEM as a Cloud Service Terminology and understand the basics of AEMaaCS structure, you are ready to log into the Admin Console for the first time!. . In detail, the most common and popular implementation of the SaaS CMS concept is represented by headless CMSs. The Story So Far. In Headless CMS the body remains constant i. Tap or click the folder that was made by creating your configuration. Next, explore the power of AEM’s GraphQL API using the built-in GraphiQL IDE. Allowing for bulk delivery of exactly what is needed for rendering as the response to a single API query. Author in-context a portion of a remotely hosted React application. What is Headless CMS CMS consist of Head and Body. How do they work? What are the alternatives and differences? Why would you want to use a Headless CMS?AEM. The Story So Far. The leading Open-Source Headless CMS. Headless CMS. Adobe Experience Manager Assets is a DAM that gives you automation and tools to rapidly source, adapt, and deliver your assets across audiences and channels so you can spend less time. For headless, your content can be authored as Content Fragments. Headless or No Headless, That Is the Question. Headless implementation forgoes page and component. A headless CMS is therefore responsible for the (backend) content management services, together with the mechanisms allowing the (frontend) applications to access. Learn how the Universal Editor enables what-you-see-is-what-you-get (WYSIWYG) editing of any headless and headful experience. You can review the notable changes introduced and understand what it takes to. The ability to provide actual omnichannel experiences is therefore at your disposal, giving you the. The platform allows you to manage. First name *. ”. Read the report now >. A headless content management system (CMS) is a content repository that allows you to deliver content to any frontend or UI. All leading CMS products such as Drupal, WordPress, AEM and Sitecore, Kentico and others can also work in a “headless” mode. 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. Headless CMS approach. Last update: 2023-06-23. Log into AEM and from the main menu select Tools -> Assets -> Content Fragment Models. Headless is much more scalable in terms of supporting multiple downstream technologies. A headless content management system (CMS) is a content repository that allows you to deliver content to any frontend or UI. A headless CMS is a content management system (CMS) that provides backend-only functionalities, making content accessible through a GraphQL or REST API and displayable on any device possible. styling it, presenting it, and delivering it all happen in AEM. 2. Using AEM as a Hybrid CMS. This approach enables the CMS to live up to the promise of managing content in place and publishing anywhere. It then dives down into the construction of the page and how the SPA application relates to and interacts with the AEM SPA Editor. Headless CMS offer many advantages compared to traditional CMS, but the added value is also dependent on the context, the number of channels, and what you are trying to achieve with your content. Headless CMS architecture, as a subset of decoupled, shares almost all the benefits, but with the advantage of greater flexibility to publish content on different platforms. Headless implementations enable delivery of experiences across. For AEM SPA Editor to integrate a SPA into it’s authoring context, a few additions must be made to the SPA. Products such as Contentful, Prismic and others are leaders in this space. Know the prerequisites for using AEM’s headless features. A headless CMS exposes content through well-defined HTTP APIs. 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. Be familiar with how AEM supports headless and translation. Implementing Applications for AEM as a Cloud Service; Using. E very day, businesses are managing an enormous amount of content changes — sometimes as high as thousands of content changes per day. Here, the AEM will act as a mere repository, exposing content as a service in REST/ GraphQL endpoints. Learn about the different data types that can be used to define a schema. It separates content from the presentation layer (the head), creating blocks of content that can be delivered in a channel-neutral format to power any channel or experience. Production Pipelines: Product functional. With headless API-based delivery, merchants can quickly create, evaluate, and deploy shoppable experiences. Support enterprise governance and globalisation needs with a cloud-native architecture that’s always current, providing fast deployment cycles, auto-scaling and a self-healing infrastructure. Adobe Experience Manager (AEM) is the leading experience management platform. technologies. And for a lot of traditional CMSes, a browser is, ultimately, the only place your content can live. In the headless/decoupled approach it's on the developers to build the admin panel for content edition. js is a React framework that provides a lot of useful features out of the box. Get a free trial. 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. On this page. The configuration file must be named like: com. AEM GraphQL API provides a powerful query language to expose data of Content Fragments to JavaScript clients in Headless CMS implementations. The front-end developer has full control over the app. AEM combines the five modules known as sites, assets, mobile, forms, and community.