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). This video series explains Headless concepts in AEM, which includes-. Start here for a guided journey through the powerful and flexible headless features of AEM, their capabilities, and how to leverage them on your first headless development project. SPA Introduction and Walkthrough. Learn how to create, manage, deliver, and optimize digital assets. AEM offers an out of the box integration with Experience Platform Launch. In this part of the AEM Headless Developer Journey, you will understand the steps to implementing your first headless experience in AEM including planning considerations and also learn best practices to make your path as smooth as possible. Synchronization for both content and OSGi bundles. Using this path you (or your app) can: receive the responses (to your GraphQL queries). React app with AEM Headless View the source code on GitHub A full step by step tutorial describing how this React app. Navigate to the folder you created previously. It also serves as a best-practice guide to several AEM features. Before you begin your own SPA. The AEM Headless SDK. Implementing User Guide: Understand how to build and customize experiences using AEM’s powerful features by exploring these development and deployment topics. env at the root of the project. In the Site rail, click the button Enable Front End Pipeline. In the previous document of the AEM headless journey, Learn About CMS Headless Development you learned the basic theory of what a headless CMS is and you should. All this while retaining the uniform layout of the sites (brand protection. Understand Headless in AEM; Learn about CMS Headless Development;. 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. 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. com Tutorials by framework. This end-to-end tutorial continues the basic tutorial that covered the fundamentals of Adobe Experience Manager (AEM) Headless and GraphQL. The AEM SDK is used to build and deploy custom code. Adobe’s Open Web stack, providing various essential components (Note that the 6. The focus lies on using AEM to deliver and manage (un. Connectors User GuideAEM devs, join us on Nov 6 (EMEA, LATAM, NA) & Nov 15 (APAC) for Adobe Developers Live. Developers can use the JSON Preview in the Content Fragment editor to show all values of the current Content Fragment that can be returned using the GraphQL API. Get to know how to organize your headless content and how AEM’s translation tools work. Manage GraphQL endpoints in AEM. Log into AEM and from the main menu select Navigation -> Assets -> Files. Contentstack CMS for developers is a content management system for IT, offering multiple development environments and coding in your preferred SDK. For an end-to-end example of building your own single-page application that is editable with AEM starting with project setup through application routing, see the WKND SPA Tutorials: Getting Started with the AEM SPA Editor and Angular. Monitor Performance and Debug Issues. . In the Create Site wizard, select Import at the top of the left column. The following tools should be installed locally: JDK 11; Node. AEM offers the flexibility to exploit the advantages of both models in one project. 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. With Adobe Experience Manager (AEM) as a Cloud Service, Content Fragments lets you design, create, curate, and publish page-independent content. From the Component browser panel, drag-drop the Adaptive Forms - Embed (v2) component on the page. Last update: 2023-06-27. AEM Headless Content Architect Journey Overview; Content Modeling for Headless with AEM - An Introduction; Learn the Content Modeling Basics for Headless with AEM; Learn about Creating. Headless Developer Journey. AEM employs advanced digital marketing tools to improve your user's experience and gain insight into your visitors. A Content author uses the AEM Author service to create, edit, and manage content. 4. For authentication, the third-party service must retrieve an Access Token that can then be used in the GraphQL Request. For publishing from AEM Sites using Edge Delivery Services, click here. Single page applications (SPAs) can offer compelling experiences for website users. In a headless model, the content is managed in the AEM repository, but delivered via. Components are at the core of building an experience in AEM. Last update: 2023-06-27. Open command prompt and navigate to the aem-forms-addon-native-<version> folder. 8+. It is the main tool that you must develop and test your headless application before going live. In this part of the AEM Headless Developer Journey, learn about headless technology and why you would use it. This article builds on these so you understand how to create your own Content Fragment Models for your AEM headless. 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. 4. 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. Ensure you adjust them to align to the requirements of your. The SPA is implemented using: Maven AEM Project Archetype; AEM SPA Editor; Core. What’s Next. 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. Retrieving an Access Token. Front-end pipelines can be code quality pipelines or deployment pipelines. View. The journey may define additional personas with which the translation specialist must interact, but the point-of-view for. AEM 6. The tagged content node’s NodeType must include the cq:Taggable mixin. ” Tutorial - Getting Started with AEM Headless and GraphQL. Additional Resources. 5 Developing User Guide; Get started with AEM Sites - WKND Tutorial; AEM 6. Ensure that UI testing is activated as per the section Customer Opt-In in this document. Moving forward, AEM is planning to invest in the AEM GraphQL API. Different from the AEM SDK, the AEM Headless SDK is set of libraries that can be used by clients to quickly and easily interact with AEM Headless APIs over HTTP. AEM provides robust content management capabilities and exposes Headless APIs that allow developers to access content and data stored in AEM through a variety of channels and applications. It also serves as a best-practice guide to several AEM features. 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. With these operations the API lets you operate Adobe Experience Manager as a Cloud Service as a headless CMS (Content Management. These pipelines and services are built based on best practices, ensuring thorough testing and the highest code quality. Developers can use the JSON Preview in the Content Fragment editor to show all values of the current Content Fragment that can be returned using the GraphQL API. Introduction to AEM Forms as a Cloud Service. 2 and later. This journey will help you streamline your front-end. First select which model you wish to use to create your content fragment and tap or click Next. In this optional continuation of the AEM Headless Developer Journey, you learn how AEM can combine headless delivery with traditional full-stack CMS features and how you can create editable SPAs using AEM's SPA Editor framework. This allows developers to place SPA Editor-compatible components into the SPA views, and allow users to author the components’ content in AEM SPA Editor. By allowing developers to submit form data directly through APIs or backend code, headless forms help streamline workflows and improve the overall performance of web applications. To get your AEM headless application ready for. 5. To support customers with enterprise development setups, AEM as a Cloud Service fully integrates with Cloud Manager and its purpose-built, opinionated CI/CD pipelines. 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. My requirement is the opposite i. I am not able to understand how the Template is designed. Next, we’ll use the AEM Headless SDK to retrieve Content Fragment data from AEM’s GraphQL APIs. AEM Technical Foundations. An implementation of the standard GraphiQL IDE is available for use with the GraphQL API of Adobe Experience Manager (AEM) as a Cloud Service. Tap or click Create. In the last step, you fetch and. Confirm with Create. js) Remote SPAs with editable AEM content using AEM SPA Editor. Learn how AEM can go beyond a pure headless use case, with. Know best practices to make your headless journey smooth,. They can be used by developers to provide website business users, editors, and administrators with the functionality to adapt their websites to changing business needs (content agility). An end-to-end tutorial illustrating how to build-out and expose content using AEM Headless. This React application demonstrates how to query content using AEM’s GraphQL APIs using persisted queries. 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. Tap Adaptive Forms Custom Components Migration and in the Custom Components Migration page, tap Start Migration. Guide: Developers new to AEM and headless: 1 hour: Headless Getting Started Guide: For experienced AEM users who need a short summary of the. The AEM administrator’s product profile is used to grant administrator privileges in the associated AEM instance. Integrating Adobe Target on AEM sites by using Adobe Launch. Log into AEM and from the main menu select Tools -> General -> Configuration Browser. Headless Developer Journey. Now that you have created some content fragments, you can use AEM’s APIs to deliver them headlessly. Developer. For authoring AEM content for Edge Delivery Services, click here. 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. Authoring Concepts. This setup establishes a reusable communication channel between your React app and AEM. The article contains recommendations, reference materials, and resources for developers of Assets as a Cloud Service. 1. Level 1: Content Fragment Integration - Traditional Headless Model. The command creates a directory called react-starter-kit-aem-headless-forms in your current location and clones the Headless adaptive forms React starter app into it. The AEM Headless SDK is available for various platforms: AEM Headless SDK for client-side browsers (JavaScript) AEM Headless SDK for server-side/Node. x. AEM Headless as a Cloud Service. . The AEM Headless SDK is set of libraries that can be used by clients to quickly and easily interact with AEM Headless APIs over HTTP. The Best Practices Analyzer provides an assessment of your current AEM implementation by indicating areas that are not following AEM best practices. The following tools should be installed locally: JDK 11; Node. This guide focuses on the full headless implementation model of AEM. This guide focuses on the full headless implementation model of AEM. Select the authentication scheme. 5. Start here for a guided journey through the powerful and flexible headless features of. 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. 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. Translating Headless Content in AEM. It has pre-formatted components containing. The AEM users product profile is typically. The SPA is implemented using: Maven AEM Project Archetype; AEM SPA Editor; Core. Log into AEM and from the main menu select Tools -> Assets -> Content Fragment Models. AEM offers the flexibility to exploit the advantages of both models in one project. Navigate to Tools > General > Content Fragment Models. NOTE. See full list on experienceleague. This guide uses the AEM as a Cloud Service SDK. This document is intended as a high-level quick start guide for the key page authoring actions in AEM. The following tools should be installed locally: JDK 11;. AEM’s headless features. The SPA is implemented using: Maven AEM Project Archetype; AEM SPA Editor; Core. The React App in this repository is used as part of the tutorial. Log into AEM and from the main menu select Tools -> General -> Configuration Browser. 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. The GraphQL API lets you create requests to access and deliver Content Fragments. Traditional CMS uses a “server-side” approach to deliver content to the web. Ensure that your local AEM Author instance is up and running. The Title should be descriptive. Log into AEM as a Cloud Service and from the main menu select Navigation > Assets > Files. The Experience Manager Developer Tools for Eclipse comes with a sample, multi-module project that helps you quickly get up to speed with a project setup in Eclipse. 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). 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. Asset microservices provides for scalable and resilient processing of assets using cloud-native applications (also called workers). The tools provided are accessed from the various consoles and page editors. The Assets console lets you import and manage digital assets such as images, videos, documents, and audio files. The new reference site and accompanying tutorial covers fundamental. Sample Multi-Module Project. Adobe Experience Manager projects can be implemented in both headful and headless models, but the choice is not binary. 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. Adobe Experience Manager projects can be implemented in both headful and headless models, but the choice is not binary. In this context, extending AEM as a Cloud Service, an overlay means to take the predefined. Clone the app from Github by executing the following command on the command line. Each guide builds on the previous, so it is recommended to. 5 the GraphiQL IDE tool must be manually installed. Your template is uploaded and can. Headless Developer Journey: Explore this guided journey through the powerful and flexible headless features of AEM to prepare for your first. The Create new GraphQL Endpoint dialog box opens. 8. Use GraphQL schema provided by: use the drop-down list to select the required configuration. Headless Developer Journey: Explore this guided journey through the powerful and flexible headless features of AEM to prepare for your first. Adobe Experience Manager headless CMS gives you all the tools you need to manage your content and make it available via APIs to any number of front ends via both JSON and GraphQL. Prerequisites. Implementing User Guide: Understand how to build and customize experiences using AEM’s powerful features. Click into the new folder and create a teaser. An end-to-end tutorial illustrating how to build-out and expose content using AEM Headless. 04. The AEM SDK. A headless CMS is therefore responsible for the (backend) content management services, together with the mechanisms allowing the (frontend) applications to access that content. Experience League. Topics: Onboarding. The changes go through a deployment pipeline allowing for the same code quality and security gates as in production deployment pipelines. At One Inside, our expertise relies on the implementation of the Adobe CMS, Adobe Experience Manager (AEM). Log into AEM and from the main menu select Tools -> Assets -> Content Fragment Models. Confirm and your site is adapted. Introduction. By leveraging AEM Headless APIs, you can retrieve content, assets, and data from your AEM instance and use them to power your React application. Learn how to build next-generation apps using headless technologies in Experience Manager as a Cloud Service. To validate the package, click More -> Validate, In the modal dialog box that then appears, use the checkboxes to select the type (s) of validation and begin the validation by clicking Validate. js) Remote SPAs with editable AEM content using AEM SPA Editor. Developer and Deployment Manager Tasks. Headless Developer Journey: Explore this guided journey through the powerful and flexible headless features of AEM to prepare for your first headless project. Sign In. The creation of a Content Fragment is presented as a wizard in two steps. AEM provides robust content management capabilities and exposes Headless APIs that allow developers to access content and data stored in AEM through a variety of channels and applications. Target libraries are only rendered by using Launch. How to organize and AEM Headless project. 4. Preview URLs, using URL expressions, are set on the Content Fragment Model’s Properties. Navigate to show the page for which you want to create a version. Tap or click Create -> Folder. AEM is a robust platform built upon proven, scalable, and flexible technologies. Learn how AEM can go beyond a pure headless use case, with options for in-context authoring and experience management. AEM headless CMS gives developers the freedom to build and deliver exceptional experiences using the languages, frameworks, and tools they’re already familiar with. Tap or click the folder that was made by creating your configuration. Provides links to the detailed documentation. Create your first React Single Page Application (SPA) that is editable in Adobe Experience Manager AEM with the WKND SPA. Hence, AEM uses GraphQL to exchange commerce data with Adobe Commerce and with any commerce engine via I/O Runtime. In the second step, you map your UI components or use a public UI components library, such as Google Material UI or Chakra UI to style your forms. Front end developer has full control over the app. In Projects, tap/click Create to open the Create Project wizard: Select a template and click Next. Provide a Title for your configuration. Understand how it can help content authors deliver exceptional experiences, increase their content velocity, and how provides a state-of-the-art developer experience. The React app should contain one instance of the <Page> component exported from @adobe/aem-react-editable-components. Learn how AEM can go beyond a pure headless use case, with options for in-context authoring and experience management. This GraphQL API is independent from AEM’s GraphQL API to access Content. Ask role-relevant questions. Dynamic Media is now part of AEM Assets and works the same way. Headless Developer Journey: Explore this guided journey through the powerful and flexible headless features of AEM to prepare for your first headless project. Developers want to be able to build sites using SPA frameworks and authors want to seamlessly edit content within AEM for a site built using such frameworks. The tutorial is designed to work with AEM as a Cloud Service and is backwards compatible with AEM 6. A development environment allows your developers to implement, and test AEM applications under the same runtime conditions as the stage and production environments. For Production programs, access to the Developer Console is defined by the “Cloud Manager - Developer Role” in the Admin Console, while for sandbox programs, the Developer Console is available to any user with a product profile giving them access to AEM as a Cloud Service. First select which model you wish to use to create your content fragment and tap or click Next. AEM 6. We can show you what AEM can do in regards to content. Navigate to the Software Distribution Portal > AEM as a Cloud Service. Please can someone guide me on this, also if there is a reference/ example of doing this,. 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. Resource Description Type Audience Est. Project Setup Details. This document provides and overview of the different models and describes the levels of SPA integration. js v18; Git; 1. Learn how to create a SPA using the React JS framework with AEM's SPA Editor. AEM understands every business's need for headless content management while building a foundation for future growth. Admin. This involves structuring, and creating, your content for headless content delivery. Developing SPAs for AEM. When creating a GraphQL query, developers can choose different response types from html, plaintext, markdown, and json from a multi-line field. Last update: 2023-11-17. For example, when publishing, an editor has to review the content - before a site administrator activates the page. Asset microservices lets you process a broad range of file types covering more formats out-of-the-box than. After reading you should: Understand the basic concepts and terminology of headless content delivery 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. Permission considerations for headless content. They can be requested with a GET request by client applications. Start the React tutorial. 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. You also learn how you can create editable SPAs using AEM’s SPA Editor framework, and integrate external SPAs, enabling editing capabilities as required. Select the root of the site and not any child pages. The main characteristics of a traditional CMS are: Authors generate content with WYSIWYG editors and use predefined templates. After reading it, you can do the following: From these takeaways we can recommend AEM headless or hybrid to be considered when the following points are met: You aim to deliver the same experience and code base for a content-focused page on the web and a hybrid mobile app. The changes go through a deployment pipeline allowing for the same code quality and security gates as in production deployment pipelines. Headless Developer Journey: Explore this guided journey through the powerful and flexible headless features of Experience Manager to prepare for your. Rich text with AEM Headless. For the purposes of this getting started guide, you are creating only one model. CRXDE Lite is embedded into CRX/AEM and enables you to perform standard development tasks in the browser. Each environment contains different personas and with. Be aware of AEM’s headless integration levels. In the previous document of the AEM headless translation journey, Get started with AEM headless translation you learned how to organize your headless content and how AEM’s translation tools work and you should now: Understand the importance. However, headful versus headless does not need to be a binary choice in AEM. Tutorials by framework. 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. An AEM installation generally consists of at least two environments: Author. Customise and extend the functionality of your CMS with our headless capabilities, API-first architecture and vast number of integrations. Developer. cqModel Understand the candidate’s career goal, professional interests, etc. Build a React JS app using GraphQL in a pure headless scenario. 5 is a flexible tool for the headless implementation model by offering three powerful services: Content Models. Start the React tutorial. This guide uses the AEM as a Cloud Service SDK. Select Create. Search for. Enable developers to add automation to. Tap or click the folder you created previously. Assets Guide; AEM 6. The tutorial is designed to work with AEM as a Cloud Service and is backwards compatible with AEM 6. Select Create at the top-right of the screen and from the drop-down menu select Site from template. The Content author and other. Creating a. In the previous document of the AEM headless journey, How to Model Your Content you learned the basics of content modeling in AEM,. TIP If you are new to AEM as a Cloud Service and familiar with AEM. Connectors User Guide 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. Deployment Managers - These users use Cloud Manager to create and run pipelines that deploy the code from the git repositories to your running AEM environments. Adobe Experience Manager (AEM) is the leading experience management platform. Time; Headless Developer Journey: For users new to AEM and headless technologies, start here for a comprehensive introduction to AEM and its headless features from the theory of headless through going live with your first headless project. Users with the Cloud Manager User role only can log into Cloud Manager and navigate to the AEM author environments (if they exist) by using the Programs menu options. Headless Developer Journey - Start here for a guided course for developing headless applications with AEM. 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. A development environment allows your developers to implement, and test AEM applications under the same runtime conditions as the stage and production environments. AEM as a Cloud Service technical documentation - If you already have a firm understanding of AEM and headless technologies, you may want to. AEM_Forum. 4. Developer. 20. Then Getting Started with AEM Headless as a Cloud Service described AEM Headless in the context of your own project. . Experience League. Headless features can be used to manage and deliver content to multiple touch-points, while also enabling content authors to edit single page applications. Guide: Developers new to AEM and headless: 1 hour: Headless Setup: For experienced AEM users who need a short summary of the key AEM. It has Logo, Tagline. In a headless setup, the presentation system (the head) is decoupled from the content management (the tail). To open the panel, select Developer from the mode selector in the toolbar of the page editor: The panel is divided into two tabs: Components - This shows a component tree, similar to the content tree for authors. The AEM Quick Site Creation tool allows non-developers to quickly create a site from scratch by using site templates. In this part of the journey, you learn how to plan and perform the migration once both the code and the content are ready to be moved over to AEM as a Cloud Service. For an overview of all of the available components in your AEM instance, use the Components Console. The platform is also extensible, so you can add new APIs in the future to deliver content in a different. Implementing User Guide: Understand how to build and customize experiences using AEM’s powerful features by exploring these development and deployment topics. Objective. Adobe Experience Manager projects can be implemented in both headful and headless models, but the choice is not binary. Log into AEM as a Cloud Service and from the main menu select Navigation -> Content Fragments. We believe it is beneficial for any developer involved in an AEM SPA Editor project to complete this tutorial. 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. For a third-party service to connect with an AEM instance it must have an. This is the same framework used to translate other AEM content, such as Pages, Experience Fragments, Assets, and Forms. 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. Path to Your First Experience Using AEM Headless. Learn how AEM can go beyond a pure headless use case, with. Before you configure front-end pipelines, review the AEM Quick Site Creation Journey for an end-to-end guide through the easy-to-use AEM Quick Site Creation tool. Each guide builds on the previous, so it is recommended to explore them thoroughly and in order. In this chapter, we replace the Home view’s title, “Current Adventures”, which is hard-coded text in Home. This guide uses the AEM as a Cloud Service SDK. Next, explore the power of AEM’s GraphQL API using the built-in GraphiQL Explorer. With your site selected, open the rail selector at the left and choose Site. The tutorial covers fundamental topics like project setup, maven archetypes, Core. The GraphiQL Explorer tool enables developers to create, and test queries against content on the current AEM environment. Last update: 2023-08-16. Open the Templates Console (via Tools -> General) then navigate to the required folder. Here you can specify: Name: name of the endpoint; you can enter any text. This multi-part tutorial walks through the implementation of a React application for a fictitious lifestyle brand, the WKND. In summary: from an administrator’s point of view, configurations are how you create workspaces to manage settings in AEM, whereas the developer should understand how AEM uses and manages these. This document helps you understand the AEM headless publication pipeline and the performance considerations you must be aware of before you go live with your application. 5. The AEM Headless SDK is available for various platforms: AEM Headless SDK for client-side browsers (JavaScript) AEM Headless SDK for server-side/Node. Persisted queries are GraphQL queries that are created and stored on the Adobe Experience Manager (AEM) as a Cloud Service server. For publishing from AEM Sites using Edge Delivery Services, click here. 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. This guide uses the AEM as a Cloud Service SDK. Creating a. This allows the front-end developer, who need zero knowledge of. from other headless solution to AEM. js) Remote SPAs with editable AEM content using AEM SPA Editor. Select AEM in the dialog and click Open. Looking for a hands-on tutorial? Last update: 2023-08-16. This user guide contains videos and tutorials on the many features and capabilities of AEM Sites. Use GraphQL schema provided by: use the drop-down list to select the required configuration. This pattern can be used in any SPA and Widget approach but does make AEM more developer-focused. Navigate to the folder you created previously. 8+. Author in-context a portion of a remotely hosted React application. 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.