A primary use case for The Adobe Experience Manager as a Cloud Service (AEM) GraphQL API for Content Fragment Delivery is to accept remote queries from third-party applications or services. This component is able to be added to the SPA by content authors. The auto-generated AEM page must have its type changed to Remote SPA page , rather than a SPA page . 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. 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. In a headless setup, the presentation system (the head) is decoupled from the content management (the tail). All Rights Reserved. Created for: Beginner. This typical setup showcases an example of migration from a traditional setup to a completely headless setup (with Contentstack as your headless CMS), the recommended way is to migrate one site at a. In a typical development cycle, you start with creating and hosting Headless adaptive forms on Adobe Experience Manager Forms Server. This document. This tutorial explores how AEM Content Services can be used to power the experience of an Mobile App that displays Event information (music, performance, art, etc. Topics: Content Fragments. The ImageRef type has four URL options for content references: _path is the referenced path in AEM. Session description: There are many ways by which we can. Start here for a guided journey through the powerful and flexible headless features of AEM, their capabilities, and how to use them on your project. 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-context authoring. A modern content delivery API is key for efficiency and performance of Javascript-based frontend applications. A Headless Content Management System (CMS) is a back-end only content management system, designed and built explicitly as a content repository that makes content accessible via an API, for display on any device. Adobe Confidential. This document. Or in a more generic sense, decoupling the front end from the back end of your service stack. A modern content delivery API is key for efficiency and performance of Javascript-based frontend applications. What you need is a way to target specific content, select what you need and return it to your app for further processing. AEM, as a headless CMS, has become popular among enterprises. The AEM Headless Client for JavaScript is used to execute the GraphQL persisted queries that power the app. In the file browser, locate the template you want to use and select Upload. These remote queries may require authenticated API access to secure headless content delivery. The ImageRef type has four URL options for content references: _path is the referenced path in AEM. Authoring for AEM Headless as a Cloud Service - An Introduction: An introduction to the headless features of Adobe Experience Manager as a Cloud Service, and how to author content for your project. The most common deployment pattern with AEM headless applications is to have the production version of the application connect to an AEM Publish service. The power of AEM allows it to deliver content either headlessly, full-stack, or in both. 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. For publishing from AEM Sites using Edge Delivery Services, click here. In the future, AEM is planning to invest in the AEM GraphQL API. Universal Editor Introduction. If auth is not defined, Authorization header will not be set. Custom registration code can be written that takes, minimally, the end user’s username and password, and creates a user record in AEM which can then be used to authenticate against during login. Regardless of which model you choose to implement for SSR, you must specify to AEM how to access this remote rendering service. 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. A headless CMS i s a content management system (CMS) that lets you take content from the CMS and deliver it to any front end using any framework of choice. Tap or click Create -> Content Fragment. You signed in with another tab or window. json to be more correct) and AEM will return all the content for the request page. AEM Forms Headless Adaptive Forms provide a fast and efficient way to create forms for various platforms including Headless or Headful CMS, React applications, Single Page Applications (SPA), Web Apps, Mobile apps, Amazon Alexa, Google Assistant, WhatsApp, and more. They can also reuse content across sites, easily manage metadata and tagging, and accelerate translation to quickly build better digital journeys for your customers. Tap on the download button in the top-left corner to download the JSON file containing accessToken value, and save the JSON file to a. The two only interact through API calls. You should now: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. With Headless Adaptive Forms, you can streamline the process of building. Scheduler was put in place to sync the data updates between third party API and Content fragments. In this part of the AEM Headless Developer Journey, learn about headless technology and why you would use it. Implementing Applications for AEM as a Cloud Service; Using. The session will be split in two halves as follows: Part 1: AEM as a headless CMS Where/When/Why? Presenter: Vengadesh Shanmugavelu - Technical Architect, Qatar Airways. We’ll cover retrieving Content Fragment data from AEM’s GraphQL APIs and displaying it in the React app. 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. html with . The multi-line text field is a data type of Content Fragments that enables authors to create rich text content. 10. In a headless setup, the presentation system (the head) is decoupled from the content management (the tail). In a typical development cycle, you start with creating and hosting Headless adaptive forms on Adobe Experience Manager Forms Server. To allow developers to easily fuel content into multiple touchpoints, we are introducing GraphQL APIs for headless content delivery. The tagged content node’s NodeType must include the cq:Taggable mixin. 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. 5 is a flexible tool for the headless implementation model by offering three powerful services: Content Models. An implementation of the standard GraphiQL IDE is available for use with the GraphQL API of Adobe Experience Manager (AEM) as a Cloud Service. It is the main tool that you must develop and test your headless application before going live. This guide contains videos and tutorials on the many features and capabilities of AEM. Understand how to build and customize experiences using AEM’s powerful features by exploring these development and deployment topics. A headless CMS i s a content management system (CMS) that lets you take content from the CMS and deliver it to any front end using any framework of choice. Translating Headless Content in AEM. The site creation wizard starts. In this session, we will cover the following: Content services via exporter/servlets. AEM’s GraphQL APIs for Content Fragments. Discover the Headless CMS capabilities in Adobe Experience Manager. Create Content Fragments based on the. The. Getting Started with AEM SPA Editor. You signed out in another tab or window. js application demonstrates how to query content using AEM’s GraphQL APIs using persisted queries. js and click on the Install option. This session dedicated to the query builder is useful for an overview and use of the tool. Select the folder or select one or more assets within the folder. The session will be split in two halves as follows: Part 1: AEM as a headless CMS Where/When/Why? Presenter: Vengadesh Shanmugavelu - Technical Architect, Qatar Airways. The Story So Far. The journey defines additional personas with which the developer must interact for a successful project, but the point-of-view for the journey is that of the developer. 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. These remote queries may require authenticated API access to secure headless content. The creation of a Content Fragment is presented as a wizard in two steps. Contributions are welcome! Read the Contributing Guide for more information. 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. The two only interact through API calls. This React application demonstrates how to query content using AEM’s GraphQL APIs using persisted queries. Learn to create a custom AEM Component that is compatible with the SPA editor framework. For each core product — Experience Manager Sites and. 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. 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. See full list on experienceleague. ” Tutorial - Getting Started with AEM Headless and GraphQL. This Next. The Story So Far. The term “headless” comes from the concept of chopping the “head” (the front end, i. This guide provides an overview of Experience Manager as a Cloud service, including an introduction, terminology, architecture, and so on. Content models. When. Learn how to connect AEM to a translation service. The AEM Headless Client for JavaScript is used to execute the GraphQL persisted queries that power the app. 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. On the toolbar, click Download. Understand how to build and customize experiences using AEM’s powerful features. For the latter, however, it really is a toss-up. Let’s define what a headless CMS is now. AEM provides a Translation Integration Framework for headless content, allowing Content Fragments and supporting assets to be easily translated for use across locales. Experience Manager Sites is the only CMS that enables every marketer to create and edit webpages quickly. Tap Get Local Development Token button. In terms of authoring Content Fragments in AEM this means that:Meet the headless CMS that powers connected experiences everywhere, faster. 10. Learn about key AEM 6. js file under /utils that is reading elements from the . Authorization. It provides a middle ground. The below video demonstrates some of the in-context editing features with. You also learn how you can create editable SPAs using AEM’s SPA Editor framework, and integrate external SPAs, enabling editing capabilities as required. AEM Headless APIs allow accessing AEM content from any. The headless part is the content backend, as a headless Content Management System (CMS) is a back-end only content management system, designed and built explicitly as a content repository that makes content accessible via an API, for display on any device. Select the Extension Catalog option, and search for Target in the filter. First select which model you wish to use to create your content fragment and tap or click Next. The Story So Far. Select the Extension Catalog option, and search for Target in the filter. Peter Nealon, Vice President, Engineering of ASICS Digital. Start here for an overview of the guided journeys available to understand AEM’s powerful headless features. Explore tutorials by API, framework and example applications. This class provides methods to call AEM GraphQL APIs. granite. Cockpit is a free, open-source and self-hosted headless CMS that describes itself as a “content provider” and “not a website builder. AEM GraphQL API requests. In this part of the AEM Headless Developer Journey, learn about what is required to get your own project started with AEM Headless. After a user creates a Content Fragment based on the Article model, it can then be interrogated through GraphQL. The Assets REST API offered REST-style access to assets stored within an AEM instance. Adobe Experience Manager. 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. SPA Editor Single Page App in React or Angular. Clients can send an HTTP GET request with the query name to execute it. You also learn how you can create editable SPAs using AEM's SPA Editor framework, and integrate external SPAs, enabling editing capabilities as required. Adobe Experience Manager projects can be implemented in both headful and headless models, but the choice is not binary. Learn about fluid experiences and its application in managing content and experiences for either headful or. The AEM Project Archetype generates a project primed for AEM’s integration with a Remote SPA, but requires a small, but important adjustment to auto-generated AEM page structure. The context. Examples can be found in the WKND Reference Site. Then the Content Fragments Models can be created and the structure defined. 5. Learn how Experience Manager as a Cloud Service works and what the software can do for you. . 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. With these operations the API lets you operate Adobe Experience Manager as a Cloud Service as a headless CMS (Content Management. Tap/click the asset to open its asset page. Headless Developer Journey. 1. Start here for a guided journey through the powerful and flexible headless features of AEM, their capabilities, and how to use them on your project. A Content author uses the AEM Author service to create, edit, and manage content. Conclusion. Start here for a guided journey through the powerful and flexible headless features of AEM, their capabilities, and how to leverage them on your project. 1. 2. Permissions and personas can broadly be considered based on the AEM environment Author or Publish. The CORS configuration must specify a trusted website origin alloworigin or alloworiginregexp for which access must be granted. We are looking to integrate with the Adobe headless-CMS version of the AEM. The typical use case being our clients have a complete AEM suite and we would like to pull down assets within the CMS for them to use within our application. Tap the Local token tab. e. Authorable components in AEM editor. 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. 0(but it worked for me while. In this optional continuation of the AEM Headless Developer Journey, you learn how Adobe Experience Manager (AEM) can combine headless delivery with traditional full-stack CMS features and how you can create editable SPAs using AEM’s SPA Editor framework, and integrate external SPAs, enabling editing capabilities as required. Developer. The two only interact through API calls. cfg. 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. With Headless Adaptive Forms, you can streamline the process of. Personalize & Adobe Experience Manager. AEM as a Cloud Service and AEM 6. Understand how it can help content authors deliver exceptional experiences, increase their content velocity, and how. In the previous document of the AEM headless journey, Getting Started with AEM Headless as a Cloud Service you learned the basic theory of what a headless CMS is and you should now: Understand the basics of AEM’s headless features. AEM Headless as a Cloud Service. A “headless” CMS is a content management system that lets you take content from a CMS and deliver it to any front end using any framework of choice. Author in-context a portion of a remotely hosted React application. A headless CMS can feel more future-proof since you can change out the front-end as the web evolves, but it is reliant on developers to make changes or refreshes when the site needs them. With Adobe Experience Manager content and commerce, brands can scale and innovate faster to differentiate commerce experiences and capture accelerating online spend. Adobe Experience Manager headless CMS is the most flexible content management system that helps teams quickly build and deliver customer experiences across all channels and devices. Content creation. Looking for a hands-on. The journey lays out the requirements, steps, and approach of an AEM Headless project from the perspective of a Content Architect. New AI-powered and no-code features coming to Adobe Experience Manager (AEM) will enable marketers to create personalized content at scale with greater effectiveness. Deploying a SPA that interacts AEM in a headless manner involves hosting the SPA and making it accessible via a web. GraphiQL is included in all environments of AEM (but will only be accessible/visible when you configure your endpoints). SPA Editor learnings. The AEM Headless Client for JavaScript is used to execute the GraphQL persisted queries that power the app. A headless CMS i s a content management system (CMS) that lets you take content from the CMS and deliver it to any front end using any framework of choice. The GraphiQL tool enables developers to create and test queries against content on the current AEM environment. It is the main tool that you must develop and test your headless application before going live. An introduction to using the features of Adobe Experience Manager as a Cloud Service as a Headless CMS to author content for your project. The Create new GraphQL Endpoint dialog box opens. What is Headless CMS . The power of AEM allows it to deliver content either headlessly, full-stack, or in both models at the same time. 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. This React. Welcome to this tutorial chapter where we will explore configuring a React app to connect with Adobe Experience Manager (AEM) Headless APIs using the AEM Headless SDK. An implementation of the standard GraphiQL IDE is available for use with the GraphQL API of Adobe Experience Manager (AEM). Adobe Experience Manager is a hybrid CMS that offers you the best of both worlds. A headless CMS i s a content management system (CMS) that lets you take content from the CMS and deliver it to any front end using any framework of choice. Clone and run the sample client application. AEM Headless APIs allow accessing AEM. Here you can specify: Name: name of the endpoint; you can enter any text. The power of AEM allows it to deliver content either headlessly, full-stack, or in both. Adobe Experience Manager supports a headless approach, freeing it from being bound to its historical Java-based web development. What you need is a way to target specific content, select what you need and return it to your app for further processing. This session will cover the following - Content services via exporter/servlets Content fragment via asset API (demo) Content fragment via Graphql (demo) Some real. To get your AEM headless application ready for. Target libraries are only rendered by using Launch. Confirm with Create. Deliver personalized, content-led. The following Documentation Journeys are available for headless topics. Content fragment via asset API (demo) Content fragment via graphql (demo) Some real-time use cases around using content fragments and their approaches. The. Next, explore the power of AEM’s GraphQL API using the built-in GraphiQL IDE. 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. Experience League. An AEM project is required to setup-supporting configuration and content requirements to allow AEM SPA Editor to author a Remote SPA. Get ready for Adobe Summit. AEM’s GraphQL queries can be written to provide URLs to images based on where the image is referenced from. 3. Example applications are a great way to explore the headless capabilities of Adobe Experience Manager (AEM). Start here for a guided journey through the powerful and flexible headless features of AEM, their capabilities, and how to leverage them on your project. A Headless Content Management System (CMS) is a back-end only content management system, designed and built explicitly as a content repository that makes content accessible via an API, for display on any device. ) that is curated by the. The frontend, which is developed and maintained independently, fetches content from the. Enable developers to add automation. They can also reuse content across sites, easily manage metadata and tagging, and accelerate translation to quickly build better digital journeys for your customers. 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. Content Fragments used in AEM Headless content modeling, often reference image assets intended for display in the headless experience. Select the Configure button. SPA Editor Single Page App in React or Angular. Once headless content has been. A Headless Content Management System (CMS) is a back-end only content management system, designed and built explicitly as a content repository that makes content accessible via an API, for display on any device. Looking at this at a high level, AEM at the bottom of the stack, will act as a headless CMS and expose content as JSON using AEM Content Services APIs. Learn about the concepts and mechanics of authoring content for your Headless CMS using Content Fragments. Content models. Learn about headless technologies, why they might be used in your project,. supports headless CMS scenarios where external client applications render experiences using content managed in AEM. Clients can send an HTTP GET request with the query name to execute it. This tutorial explores how AEM’s GraphQL APIs and headless capabilities can be used to power the experiences surfaced in an external app. They can be requested with a GET request by client applications. In Headless CMS the body remains constant i. Integrating Adobe Target on AEM sites by using Adobe Launch. Due to this approach, a headless CMS does not. This document provides and overview of the different models and describes the levels of SPA integration. In this optional continuation of the AEM Headless Developer Journey, you learn how AEM can combine headless delivery with traditional full-stack CMS features. Adobe Experience Manager headless CMS is the most flexible content management system that helps teams quickly build and deliver customer experiences across all channels and devices. 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. NOTE. In this part of the AEM Headless Developer Journey, learn about what is required to get your own project started with AEM Headless. AEM as a Cloud Service GraphQL API used with Content Fragments is heavily based on the standard, open source GraphQL API. Sorted by: 1. Headless Developer Journey: Explore this guided journey through the powerful and flexible headless features of AEM to prepare for your first headless project. By making the switch to Contentstack, we’ll be able to provide creative, unique content experiences and operate with speed and flexibility for years to come. In this part of the AEM Headless Developer Journey, learn about headless technology and why you would use it. Getting Started with AEM Headless as a Cloud Service. Create Content Fragments based on the. At its simplest level, creating digital experiences in AEM requires the following steps: Your content authors create your headless content in the author instance. In the future, AEM is planning to invest in the AEM GraphQL API. What is a headless CMS? A headless CMS decouples the management of the content from its presentation completely. Using the API a developer can formulate queries that select specific content. 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. As part of its headless architecture, AEM is API-driven. API Reference. In the previous document of the AEM headless translation journey, Translate Content, you learned how to use AEM Translation Projects to translate your headless content. Learn about the concepts and mechanics of authoring content for your Headless CMS using Content Fragments. Tap the ellipsis next to the environment in the Environments section, and select Developer Console. 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,. Persisted queries are queries that are stored on the Adobe Experience Manager (AEM) server. From the sites console, tap or click Create at the top-right of the screen and select Site from template in the drop-down. styling it, presenting it, and delivering it all happen in AEM. GraphQL, an industry standard, application-agnostic query language to retrieve content, lets developers get exactly the content they need —. Experience Manager Sites is the only CMS that lets any marketer create and edit webpages using familiar tools such as Microsoft Word or Google Docs. The <Page> component has logic to dynamically create React components based on the. This journey provides you with all the information you need to develop. Give marketers a simple drag-and-drop interface to make layout and page structure adjustments for web or app experiences with a live preview to ensure that it. 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. For headless, your content can be authored as Content Fragments. Creating Content Fragment Models. Digital asset management. Developer docs and APIs references; Folder metadata schema;. Connectors User Guide© 2022 Adobe. Be aware of AEM’s headless integration levels. Before calling any method initialize the instance with GraphQL endpoint, GraphQL serviceURL and auth if needed Typedefs Model: object . ; Be aware of AEM's headless. Quick insight. Organize and structure content for your site. endpoint is the full path to the endpoint created in the previous lesson. AEM Content Fragments work together with the AEM GraphQL API (a customized implementation,. A collection of Headless CMS tutorials for Adobe Experience Manager. AEM: Headless vs. adobe. In this part of the AEM Headless Developer Journey, learn about what is required to get your own project started with AEM Headless. The following AEM documentation includes everything from essential guides for those new to the content management system (CMS) to videos, tutorials, and further learning resources to get the most out of AEM 6. 10. 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. This means you can realize headless delivery of. Content Models serve as a basis for Content. With Headless Adaptive Forms, you can streamline the process of building. Developer. In a headless setup, the presentation system (the head) is decoupled from the content management (the tail). Once headless content has been translated,. impl. Example applications are a great way to explore the headless capabilities of Adobe Experience Manager (AEM). Headless CMS. A headless CMS (Content Management System) is a content management system that allows you to manage and distribute content across multiple channels, such as websites, mobile apps, and social media platforms, without being tied to a specific presentation layer. A modern content delivery API is key for efficiency and performance of Javascript-based frontend applications. A collection of Headless CMS tutorials for Adobe Experience Manager. 0 to 6. AEM offers the flexibility to exploit the advantages of both models in one project. The other fields were added automatically by AEM, and represent helpful methods to provide information about a certain Content Fragment; in this example, (the helper fields) _path, _metadata, _variations. Headless CMS. Universal Editor Introduction. See generated API Reference. In previous releases, a package was needed to install the. With Headless Adaptive Forms, you can streamline the process of building forms, making it easier to collect data from your users. A DXP is the full suite of tools powering the delivery of personalized. NOTE. 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. Persisted queries are queries that are stored on the Adobe Experience Manager (AEM) server. API Reference. Introduction. Looking for a hands-on tutorial? So in this regard, AEM already was a Headless CMS. Developer. 5. With Adobe Experience Manager (AEM) as a Cloud Service, Content Fragments lets you design, create, curate, and publish page-independent content. ; Be aware of AEM's headless integration. 2. Build a React JS app using GraphQL in a pure headless scenario. Adobe Experience Manager supports a headless approach, freeing it from being bound to its historical Java-based web development. supports headless CMS scenarios where external client applications render experiences using content managed in AEM. Discover the benefits of going headless and streamline your form creation process today. cors. Build from existing content model templates or create your own. Tutorials by framework. Created for: Beginner. If you currently use AEM, check the sidenote below. Browse the following tutorials based on the technology used. Learn the basic of modeling content for your Headless CMS using Content Fragments. This article builds on these so you understand how to model your content for your AEM headless. Understand how to create new AEM component dialogs. Content Fragments. Confirm with Create. adobe. Adobe Experience Manager as a Headless CMS - Where/When/Why?In this session, you'll learn how to implement headless CMS via Adobe Experience Manager in many ways. Headless is an example of decoupling your content from its presentation. 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. Learn about headless technologies, what they bring to the user experience, how AEM supports headless models, and how to implement your own headless development project from A to Z. Learn about the concepts and mechanics of authoring content for your Headless CMS using Content Fragments. Learn how to model content and build a schema with Content Fragment Models in AEM. Get a free trial. js (JavaScript) AEM Headless SDK for Java™. The AEM SDK is used to build and deploy custom code. Becker (@ MarkBecker), Markus Haack (@ mhaack), and Jody Arthur This is the first part of a series of the new headless architecture for Adobe Experience Manager. For ease of authoring content, having easy-to-use.