The full code can be found on GitHub. js app is built, how it connects to AEM Headless to retrieve content using GraphQL persisted queries, and how that data is presented. The following tools should be installed locally: JDK 11;. AEM WCM Core Components 2. Tap the Technical Accounts tab. The Remote Content Renderer Configuration that is required to use SSR with your SPA in. The completed SPA, deployed to AEM, can be dynamically authored with traditional in-line editing. 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. In the previous two chapters, we mapped editable component content from the SPA’s Home view to corresponding Remote SPA root page in AEM at /content/wknd. GraphQL serves as the “glue” between AEM and the consumers of headless content. The <Page> component has logic to dynamically create React components based on the. AEM GraphQL API requests. The Angular app is developed and designed to be deployed with AEM’s SPA Editor, which maps Angular components to AEM components. js app uses AEM GraphQL persisted queries to query. An end-to-end tutorial illustrating how to build-out and expose content using AEM Headless. 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. A modern content delivery API is key for efficiency and performance of Javascript-based frontend applications. 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 Adventure Detail SPA route is defined as /adventure/:slug where slug is a unique identifier property on the Adventure Content Fragment. A PDF document can have multiple annotations. This tutorial walks through the implementation of a React application for a fictitious lifestyle brand, the WKND. Build a React JS app using GraphQL in a pure headless scenario. Learn to use the delegation pattern for extending Sling Models and. Headless implementation forgoes page and component management, as is traditional in. The common use case for server-to-server AEM Headless apps is to sync Content Fragment data from AEM into other systems, however this application is intentionally. An end-to-end tutorial illustrating how to build-out and expose content using AEM Headless. The full code can be found on GitHub. There are many ways to build the web; most of the ways can be implemented in AEM, which one works best is going to depend on your authors. Also, SPAs can be used within AEM while also using AEM to deliver content to additional endpoints headlessly. The React app is intentionally simple, to focus on the integration with AEM’s GraphQL APIs. What the authors are willing to author, how involved do they get with content, and how involved do they want to get with crafting experiences? SPA - single page. Web Component/JS deployments differ from SPA deployments in that they don’t use a robust SPA framework, and are expected to be embedded in the. Remote DAM URL is the URL of the Assets location in the format [assets_servername]: [port]. The journey lays out the requirements, steps, and approach of an AEM Headless project from the perspective of a Content Architect. This guide uses the AEM as a Cloud Service SDK. The approach I am thinking of is, all fields on the SPA app can be rendered in XML/JSON via. Deploying a SPA that interacts AEM in a headless manner involves hosting the SPA and making it accessible via a web browser. The Angular app is developed and designed to be. This React application demonstrates how to query content using AEM’s GraphQL APIs using persisted queries. AEM Headless Web Component/JS deployments are pure JavaScript apps that run in a web browser, that consume and interact with content in AEM in a headless manner. js app is built, how it connects to AEM Headless to retrieve content using GraphQL persisted queries, and how that data is presented. Next page. Learn to use modern front-end tools, like the Angular's CLI tool, to rapidly develop the. In addition to pure AEM-managed content CIF, a page can. The app is reusable and portable. frontend module is a webpack project that contains all of the SPA source code. 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. 5 and React integration. Let’s create some Content Fragment Models for the WKND app. In this chapter, we replace the Home view’s title, “Current Adventures”, which is hard-coded text in Home. 4. Example applications are a great way to explore the headless capabilities of Adobe Experience Manager (AEM). Populates the React Edible components with AEM’s content. The SPA Editor offers a comprehensive solution for supporting SPAs. View the source code on GitHub. Integrate the SPA; 3 - Map SPA components; 4 - Navigation and routing; 5 - Custom component;. Tutorials by framework. zip or greater This chapter is a continuation of the Create Project chapter, however to follow along all you need is a working SPA-enabled AEM project. This server-to-server application demonstrates how to query content using AEM’s GraphQL APIs using persisted queries and print it on terminal. js app. A majority of the SPA. The page is now editable on AEM with a. Next page. Experience League. This chapter is a continuation of the Create Project chapter, however to follow along all you need is a working SPA-enabled AEM project. You can always view the finished code on GitHub or check the code out locally by switching to the branch Angular/integrate-spa-solution. Depending on the client and how it is deployed, AEM Headless deployments have different considerations. AEM provides a Translation Integration Framework for headless content, allowing Content Fragments and supporting assets to be easily translated for use across locales. An end-to-end tutorial illustrating how to build-out and expose content using AEM Headless. Before executing these steps, ensure that you have an Azure storage account and an access key to authorize the access to the Azure storage account. js (JavaScript) AEM Headless SDK for Java™. Example applications are a great way to explore the headless capabilities of Adobe Experience Manager (AEM). I have an angular SPA app that we want to render in AEM dynamically. The completed SPA, deployed to AEM, can be dynamically authored with traditional in-line. The <Page> component has logic to dynamically create React components based on the. AEM Basics. An end-to-end tutorial illustrating how to build-out and expose content using AEM Headless. The AEM Headless Client for Java is used to execute the GraphQL queries and map data to Java objects to power the app. An end-to-end tutorial illustrating how to build-out and expose content using AEM Headless. Create your first React Single Page Application (SPA) that is editable in Adobe Experience Manager AEM with the WKND SPA. apps and ui. Stop the webpack dev server and from the root of the project, deploy the changes to AEM using your Maven skills: $ cd aem-guides-wknd-spa $ mvn clean install . Learn how multiple views in the SPA can be supported by mapping to AEM Pages with the SPA Editor SDK. Digital asset management is a process for storing, organizing, and using multimedia brand assets like videos, audio files, photos, animations, and other creative files, marketing. A modern content delivery API is key for efficiency and performance of Javascript-based frontend applications. Headless integration with AEM. View example. js application demonstrates how to query content using AEM's GraphQL APIs using persisted queries. Now even AEM as a cloud service has react as inbuilt program into its archetype as part of Adobe’s best practices known to its Headless CMS architecture. The React app is developed and designed to be deployed with AEM’s SPA Editor, which maps React components to AEM components. The walkthrough is based on standard AEM functionality and the sample WKND SPA Project app. Select a folder to create the configuration and tap Create. These tests are maintained by Adobe and are intended to prevent changes to custom application code from being deployed if it breaks core functionality. Headless Developer Journey: Explore this guided journey through the powerful and flexible headless features of AEM to prepare for your first headless project. Prerequisites. This blog will work for both AEM as an AMS and AEMaaCS. On this page. 0. Create the Sling Model. Edit the WKND SPA Project app in AEM. Example server-to-server app SPA Editor Overview. Next Steps 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. apps and ui. Wrap the React app with an initialized ModelManager, and render the React app. js with a fixed, but editable Title component. apps and ui. This Web Component/JS application demonstrates how to query content using AEM's GraphQL APIs using persisted queries. An end-to-end tutorial illustrating how to build-out and expose content using AEM Headless. A headless content management application is a more complex architecture with the WCM owning the content publication and acting as a provider service for Single. AEM Headless as a Cloud Service. Update Policies in AEM. The following are examples of possible approaches for constructing URLs for AEM GraphQL API and image requests, for several popular headless frameworks and platforms. Previous page. AEM Headless SPA deployments. Following AEM Headless best practices, the Next. The. Wrap the React app with an initialized ModelManager, and render the React app. 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. In this chapter, a new AEM project is deployed, based on the AEM Project Archetype. Included in the WKND Mobile AEM Application Content Package below. Persisted queries. The AEM project is bootstrapped with a very simple starting point for the Angular SPA. Prerequisites This tutorial requires the following: AEM as a Cloud Service SDK Node. Learn how AEM can go beyond a pure headless use case, with options for in-context authoring and experience management. This tutorial walks through the implementation of a React application for a fictitious lifestyle brand, the WKND. When using the AEM React Editable Components with a SPA Editor-based React app, the AEM ModelManager SDK, as the SDK: Retrieves content from AEM; Populates the React Edible components with AEM’s content; Wrap the React app with an initialized ModelManager, and render the React app. Learn. js (JavaScript) AEM Headless SDK for. cq. Learn how to develop author dialogs and Sling Models to extend the JSON model to populate a custom component. What’s Next. Developer. Learn how to add editable fixed components to a remote SPA. apps and ui. 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. Two modules were created as part of the AEM project: ui. js app is built, how it connects to AEM Headless to retrieve content using GraphQL persisted queries, and how that data is presented. A majority of the SPA. A simple weather component is built. The HTTP GET requests from the headless app to AEM’s GraphQL APIs must be configured to interact with the correct AEM service, as. How to map aem component and react component. AEM Headless client deployments take many forms; AEM-hosted SPA, external SPA, web site, mobile app, or even server-to-server process. apps and ui. Create your first React Single Page Application (SPA) that is editable in Adobe Experience Manager AEM with the WKND SPA. This server-to-server application demonstrates how to query content using AEM’s GraphQL APIs using persisted queries and print it on terminal. To support SPA Editor’s layout mode for editable areas in the SPA, we must integrate AEM’s Responsive Grid CSS into the SPA. js app uses AEM GraphQL persisted queries to query adventure data. It also allows AEM Authors to use Product and Category Pickers and the Product Console to browse through product and. The below video demonstrates some of the in-context editing features with. Integration approach. The ui. Learn to use the delegation patter for extending Sling Models and features of Sling Resource. Tutorial Set up. View the. In this chapter, we replace the Home view’s title, “Current Adventures”, which is hard-coded text in Home. The goal of this introduction and walkthrough is to demonstrate to an AEM developer why SPAs are relevant, how they generally work, how a SPA is handled by the AEM SPA Editor, and how it is different from a standard AEM application. Depending on the client and how it is deployed, AEM Headless deployments have different considerations. Example applications are a great way to explore the headless capabilities of Adobe Experience Manager (AEM). Courses Recommended courses Tutorials Certification Events Instructor-led training Browse content library View all learning options. Setup your development environment and learn how to integrate a simple app with AEM Headless: 4: How to model your content:. The srcset and sources use a custom setParams function to append the web-optimized delivery query parameter to the _dynamicUrl of the. Experience LeagueThe AEM Headless SDK is set of libraries that can be used by clients to quickly and easily interact with AEM Headless APIs over HTTP. GraphQL is the language that queries AEM for the. json to be more correct) and AEM will return all the content for the request page. js implements custom React hooks. AEM Headless client deployments take many forms; AEM-hosted SPA, external SPA, web site, mobile app, or even server-to-server process. This server-to-server application demonstrates how to query content using AEM’s GraphQL APIs using persisted queries and print it on terminal. frontend. 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. The full code can be found on GitHub. Developer. SPA Editor. An end-to-end tutorial illustrating how to build-out and expose content using AEM Headless. Integrate the SPA; 3 - Map SPA components; 4 - Navigation and routing; 5 - Custom component;. Objects. Below is a summary of how the React application is built, how it connects to AEM Headless to retrieve content using GraphQL persisted queries, and how that data is presented. This is a critical configuration when using SPA Editor, since only AEM Components that have mapped SPA component counterparts are render-able by the SPA. Courses Recommended courses Tutorials Certification Events Instructor-led training Browse content library View all learning options. A majority of the. Using a REST API. An end-to-end tutorial illustrating how to build-out and expose content using AEM Headless. To manage permissions of groups in AEM, navigate to Tools > Security > Permissions. This is a critical configuration when using SPA Editor, since only AEM Components that have mapped SPA component counterparts are render-able by the SPA. Headless AEM is a Adobe Experience Manager setup in which the frontend. On the configuration page, tap Create to create Adobe Acrobat Sign configuration in AEM Forms. Other micro services can then be also integrated into the SPA. Prerequisites. In the sites console, select the page to configure and select View Properties. Using an AEM dialog, authors can set the location for the weather to be displayed. Learn how to add editable container components to a remote SPA that allow AEM authors drag and drop components into them. This introduction. A pipeline can be triggered by an event, such as a pull request from a source code repository (that is, a code change), or on a regular schedule to match a release cadence. react project directory. js application run from the command line to update asset metadata on AEM as a Cloud Service using Assets HTTP API. Learn how to bootstrap a remote SPA for AEM SPA Editor compatibility. js app is built, how it connects to AEM Headless to retrieve content using GraphQL persisted queries, and how that data is presented. Persisted queries. This server-to-server application demonstrates how to query content using AEM’s GraphQL APIs using persisted queries and print it on terminal. Requirements. When using the AEM React Editable Components with a SPA Editor-based React app, the AEM ModelManager SDK, as the SDK: Retrieves content from AEM; Populates the React Edible components with AEM’s content; Wrap the React app with an initialized ModelManager, and render the React app. Start by creating the components that will make up the composite component, that is, components for the image and its text. Creating a New Segment. Product functional tests are a set of stable HTTP integration tests (ITs) of core functionality in AEM such as authoring and replication tasks. AEM GraphQL API requests. You can always view the finished code on GitHub or check the code out locally by switching to the branch Angular/integrate-spa-solution. The auto-generated AEM page must have its type changed to Remote SPA page , rather than a SPA page . This simple React app uses the AEM Headless SDK to query AEM Headless APIs for an Adventure content, and displays the web-optimized image using img element with srcset and picture element. AEM Headless as a Cloud Service. As you consider implementing server-side rendering for your SPA, review for what parts of the app it is necessary. Learn how to bootstrap a remote SPA for AEM SPA Editor compatibility. Learn to use modern front-end tools, like the Angular's CLI tool, to rapidly develop the. Learn to use modern front-end tools, like a webpack dev server, to rapidly develop the SPA against the AEM JSON model API. Experience League. Depending on the client and how it is deployed, AEM Headless deployments have different considerations. If it is possible that I can render my app dynamic content in AEM using WebAPI. Headless Setup. This component is able to be added to the SPA by content authors. Following AEM Headless best practices, the iOS application uses AEM GraphQL persisted queries to. English is the default language for the. Below is a summary of how the Next. Take a look: SPA Editor 2. 1. The SPA Editor offers a comprehensive solution for supporting SPAs within AEM. Deploying a SPA that interacts AEM in a headless manner involves hosting the SPA and making it accessible via a web browser. In the previous chapter, you created and updated persisted queries using GraphiQL Explorer. Courses Recommended courses Tutorials Certification Events Instructor-led training Browse content library View all learning options. js app is built, how it connects to AEM Headless to retrieve content using GraphQL persisted queries, and how that data is presented. Headless mode is excellent if you prefer content to be delivered as an API and content editing is more form. js (JavaScript) AEM Headless SDK for Java™. Prerequisites AEM Headless SPA deployments. 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. In a real application, you would use a larger. There is a specific folder structure that AEM requires projects to be built. See how AEM powers omni-channel experiences. Tap or click the Create button and select Create ContextHub Segment. SPA Editor Overview. Sign In. This chapter is a continuation of the Create Project chapter, however to follow along all you need is a working SPA-enabled AEM project. Multiple requests can be made to collect as many results as required. This simple React app uses the AEM Headless SDK to query AEM Headless APIs for an Adventure content, and displays the web-optimized image using img element with srcset and picture element. WKND App project is the SPA to be integrated with AEM’s SPA Editor; Latest code. If you are not familiar with fluid grids, see the Introduction to Fluid Grids section at the bottom of this page. The ui. The Android Mobile App. In this chapter, we replace the Home view’s title, “Current Adventures”, which is hard-coded text in Home. Map the SPA URLs to AEM Pages. Integration approach. The AEM Headless SDK is available for various platforms: AEM Headless SDK for client-side browsers (JavaScript) AEM Headless SDK for server-side/Node. The 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. The auto-generated AEM page must have its type changed to Remote SPA page , rather than a SPA page . The implementation of this component illustrates the steps needed to create a net-new AEM component that is compatible with the AEM SPA Editor. When rendered server side, browser properties such as window size and location are not present. Here, the developer controls the app by enabling authoring rights in selected application areas. Sling Models are annotation driven Java™ “POJOs” (Plain Old Java™ Objects) that facilitate the mapping of data from the JCR to Java™ variables. The full code can be found on GitHub. Chapter 4 of the AEM Headless tutorial covers the role of AEM Editable Templates in the context of AEM Content Services. 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. Using an AEM dialog, authors can set the location for the weather to be displayed. The project used in this chapter will serve as the basis for an implementation of the WKND SPA and is built upon in future chapters. 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. Learn how multiple views in the SPA are supported using AEM Pages and the SPA Editor SDK. The goal of this introduction and walkthrough is to demonstrate to an AEM developer why SPAs are relevant, how they generally work, how a SPA is handled by the AEM SPA Editor, and how it is different from a standard AEM application. A CI/CD pipeline in Cloud Manager is a mechanism to build code from a source repository and deploy it to an environment. Client type. frontend module is a webpack project that contains all of the SPA source code. 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. This component is able to be added to the SPA by content authors. The AEM Project contains configuration and content that must be deployed to AEM. The following tools should be installed locally: JDK 11;. TIP. The full code can be found on GitHub. An end-to-end tutorial illustrating how to build-out and expose content using AEM Headless. WKND App project is the SPA to be integrated with AEM’s SPA Editor; Latest code. SPA Editor. The AEM Headless Client for JavaScript is used to execute the GraphQL persisted queries that power the app. then my scenario would be feasible This tutorial walks through the implementation of a Angular application for a fictitious lifestyle brand, the WKND. Understand how the source code for a Single Page Application (SPA) written in Angular can be integrated with an Adobe Experience Manager (AEM) Project. To support SPA Editor’s layout mode for editable areas in the SPA, we must integrate AEM’s Responsive Grid CSS into the SPA. js (JavaScript) AEM Headless SDK for. 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 following list links to the relevant resources. WKND App project is the SPA to be integrated with AEM’s SPA Editor Latest code The starting point of this tutorial’s code can be found on GitHub in the. To annotate a PDF document, perform the following steps: Go to the Assets interface, navigate to the PDF document that you want to annotate. Created for: Beginner. Click De-hibernate. Open a new command prompt and. The full code can be found on GitHub. Persisted queries. Integrate the SPA; 3 - Map SPA components; 4 - Navigation and routing;. The DAM Users is an out of the box group in AEM that can be used for “everyday” users that manage digital. 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. frontend. An end-to-end tutorial illustrating how to build-out and expose content using AEM Headless. React App. You will also collaborate with our internal partners, Solution Consultants and. Below is a summary of how the React application is built, how it connects to AEM Headless to retrieve content using GraphQL persisted queries, and how that data is presented. A majority of the SPA. The AEM Headless SDK is available for various platforms: AEM Headless SDK for client-side browsers (JavaScript) AEM Headless SDK for server-side/Node. Last update: 2023-08-16. AEM Headless client deployments take many forms; AEM-hosted SPA, external SPA, web site, mobile app, or even server-to-server process. Next page. Example applications are a great way to explore the headless capabilities of Adobe Experience Manager (AEM). js with a fixed, but editable Title component. js with a fixed, but editable Title component. To support SPA Editor’s layout mode for editable areas in the SPA, we must integrate AEM’s Responsive Grid CSS into the SPA. A single-page application is a web application or website that interacts with the user by dynamically rewriting the current web page with new data from the webserver, instead of the default method of a web browser loading entire new pages. Experience Fragments are fully laid out. Select WKND Shared to view the list of existing. AEM 6. The AEM Project contains configuration and content that must be deployed to AEM. SPA editor is excellent if you prioritise Author WYSIWYG experience over seperately hosted and deployed SPA. AEM Headless as a Cloud Service. Understand how the source code for a Single Page Application (SPA) written in Angular can be integrated with an Adobe Experience Manager (AEM) Project. This simple React app uses the AEM Headless SDK to query AEM Headless APIs for an Adventure content, and displays the web-optimized image using img element with srcset and picture element. 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. The sidekick plugin for AEM Assets supports access to: AEM Assets as. Be able to define your project in terms of scope. The following tools should be installed locally: JDK 11;. html with . AEM 6. Implementing the Integration Levels. apps and ui. Know the prerequisites for using AEM’s headless features. Learn how AEM can go beyond a pure headless use case, with options for in-context authoring and experience management. js app uses AEM GraphQL persisted queries to query. An AEM project is required to setup-supporting configuration and content requirements to allow AEM SPA Editor to author a Remote SPA. 2. 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. Single page applications (SPAs) can offer compelling experiences for website users. 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. An AEM project is required to setup-supporting configuration and content requirements to allow AEM SPA Editor to author a Remote SPA. The project fully uses the SPA Editor SDK and the frontend components are developed as a library and the content structure of the app is delegated to AEM. The Title should be descriptive. Server-to-server Node. The new Adobe Developer App Builder provides an extensibility framework for a developer to easily extend functionalities in AEM as a Cloud Service. AEM container components use policies to dictate their allowed components. The auto-generated AEM page must have its type changed to Remote SPA page , rather than a SPA page . Log into AEM as a Cloud Service and from the main menu select Tools > General > Configuration Browser. Now even AEM as a cloud service has react as inbuilt program into its archetype as part of Adobe’s best practices known to its Headless CMS architecture. SPAs can be enabled with flexible levels of integration within AEM including SPAs developed and maintained outside of AEM. Persisted queries. You can create Adaptive Forms based on a. The starting point of this tutorial’s code can be found on GitHub in the remote-spa-tutorial folder. We can build projects for AEM with a SPA(Single Page Application) as frontend (can use either Angular or React). App Builder provides a unified third-party extensibility framework for integrating and creating custom experiences that extend Adobe Experience Manager. This guide uses the AEM as a Cloud Service SDK. Sling Models are annotation driven Java™ “POJOs” (Plain Old Java™ Objects) that facilitate the mapping of data from the JCR to Java™ variables. Following AEM Headless best practices, the React application uses AEM GraphQL persisted queries to. The full code can be found on GitHub. You chose fantastic. The single-page app or single-page experience then has full control over how to layout and present this content. Learn how to create a SPA using the React JS framework with AEM's SPA Editor. Level 1: Content Fragments and. An example Java™ Android™ app that consumes content from AEM Headless GraphQL APIs. In this chapter, we replace the Home view’s title, “Current Adventures”, which is hard-coded text in Home. Deploying a SPA that interacts AEM in a headless manner involves hosting the SPA and making it accessible via a web browser. 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. js with a fixed, but editable Title component. Anatomy of the React app. AEM Headless single-page app (SPA) deployments involve JavaScript-based applications built using frameworks such as React or Vue, that consume and interact with content in AEM in a headless manner. The 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. This chapter is a continuation of the Create Project chapter, however to follow along all you need is a working SPA-enabled AEM project. Integration approach. To support SPA Editor’s layout mode for editable areas in the SPA, we must integrate AEM’s Responsive Grid CSS into the SPA. The AEM Headless SDK is available for various platforms: AEM Headless SDK for client-side browsers (JavaScript) AEM Headless SDK for server-side/Node. The following are required to follow this quick setup: AEM as a Cloud Service Sandbox environment. Two modules were created as part of the AEM project: ui. Congratulations, you have updated the SPA and explored the integration with AEM! You now know two different approaches for developing the SPA against the AEM JSON model API using a webpack dev server. Single page applications (SPAs) can offer compelling experiences for website users. Populates the React Edible components with AEM’s content. Prerequisites.