5. This provides huge productivity. Headless techniques These trends have led IT teams to consider headless content management as an option for experience management and delivery. Successive Digital. • The omnichannel platform helps to consistently reuse content and repurpose data for campaigns. Adobe Experience Manager is a hybrid CMS that offers you the best of both worlds. Customise and extend the functionality of your CMS with our headless capabilities, API-first architecture and vast number of integrations. This involves structuring, and creating, your content for headless content delivery. Time Commitment. Confirm with Create. React app with AEM Headless View the source code on GitHub A full step by step tutorial describing how this React app. The latest enhancement in AEM 6. It's easy to find the content you. Then Getting Started with AEM Headless described AEM Headless in the context of your own project. Deliver omnichannel content across many different "surfaces" including web, mobile app and desktop app. Fabric is a headless commerce platform purpose-built for growth, from the company of the same name headquartered in Seattle. It's all about reducing complexity while delivering content that spans channels, from web and mobile to in-store signs, single-page applications (SPAs), and IoT apps. It supports GraphQL. 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. The following Documentation Journeys are available for headless topics. The Content author and other. In terms of authoring Content Fragments in AEM. A headless content management system (CMS) allows you to manage and reuse digital content from a single repository and publish to web, mobile apps, and single page applications. Headless CMS is an AEM solution where content is structured and made readily available for any app to use. This decoupling allows for more dynamic and flexible content delivery, enabling organizations to adapt quickly to changing technologies and user demands. For AEM SPA Editor to integrate a SPA into it’s authoring context, a few additions must be made to the SPA. AEM 6. It supports both traditional and headless CMS operations. A multi-tenant CMS consists of a single software instance that serves multiple web properties, also known as ‘tenants. 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. With these operation the API lets you operate Adobe Experience Manager as a headless CMS (Content Management System) by providing. The GraphiQL tool enables developers to create and test queries against content on the current AEM environment. Meet the headless CMS that powers connected experiences everywhere, faster. AEM Headless is a CMS solution from Experience Manager that allows structured content (Content Fragments) in AEM to be consumed by any app over. To wrap up, the Visual SPA Editor is available now in Magnolia 6. 3. Using a REST API introduce challenges: An 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. Introducing Visual Copilot: Figma to code with AI. In this part of the onboarding journey, you learn about the preparation necessary before you can log into the system for the first time. Both AEM and Adobe Commerce are a part of Adobe’s Experience Cloud offering. This approach enables the CMS to live up to the promise of managing content in place and publishing anywhere. In the previous document of the AEM headless journey, Learn About CMS Headless Development you learned the basic theory of what a. This document helps you understand headless content delivery, how AEM supports headless, and how. Now that you have read the article AEM as a Cloud Service Terminology and understand the basics of AEMaaCS structure, you are ready to log into the Admin Console for the first time!. AEM offers the flexibility to exploit the advantages of both models in one project. Adobe vs Salesforce Adobe vs Oracle Adobe vs Sitecore See All Alternatives. The AEM SDK. This article explores the use of headless CMS in Adobe Experience Manager (AEM) and its benefits for content management and delivery. This decoupling means your content can be served into whatever head or heads you want. The headless CMS architecture is ideal for the largest of content syndication efforts as it offers robust capabilities for publication. A self-hosted and Enterprise-ready Edition. Authoring Basics for Headless with AEM. The term “headless” comes from the concept of chopping off the “head”, or in this case the presentation layer (typically the frontend website templates, pages, and views) from the body (the body being the. It supports all the standard authentication protocols including SAML SSO and LDAP and regularly releases AEM security hotfixes that can be easily installed. It decouples the front-end presentation (the website your visitors see) from the back-end CMS (the user interface your site admins see, which they use to edit the site and publish content. But, this doesn't list the complete capabilities of the CMS via the documentation. Unlike traditional CMS setups, Headless AEM focuses solely on content creation, storage, and retrieval, while leaving the rendering and delivery of content to external applications via APIs. AEM has been adding support for headless delivery for a while, starting with simply swapping the . For example, Brightspot uses a Content Delivery API and a Content Management API to support headless CMS implementation. 33 percent of that growth is going to come from. the content repository). GraphQL API. While decoupled from the back end, a hybrid CMS includes a presentation layer similar to a traditional or coupled CMS at the same time using a headless architecture for delivery. 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. Sitecore is an enterprise-grade content management system used by Puma, Subway,. 3, Adobe has fully delivered. On this page. Get Started with AEM Headless Translation. json to a published resource. 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. Log into AEM and from the main menu select Tools -> Assets -> Content Fragment Models. The design of the content is equally as free. 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. Wow your customers with AEM Headless – A discussion with Big W. That said, it is way easier with Franklin to achieve these results because they are assured by how the platform builds and delivers your content. Content Services: Expose user defined content through an API in JSON format. Next, explore the power of AEM’s GraphQL API using the built-in GraphiQL IDE. Storyblok is the headless content management system that empowers developers and content teams to create better content experiences across any digital channel. CMS Connection. Content Fragments: Allows the user to add and. If you have a pure headless CMS, you will only have a content repository and nothing else. 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. 5 is a full blown HTTP API that turns a structured content model in AEM into an asset that can be more easily consumed by external systems. Product. The AEM Developer Portal; Previous page. For headless, your content can be authored as Content Fragments. This article builds on these so you understand how to create your own Content Fragment. HubSpot doesn’t have designed instruments for headless development. In the left-hand rail, expand My Project and tap English. You can run the demo in a few minutes. AEM allows users to choose between headless and hybrid approaches depending on their requirements. This end-to-end tutorial continues the basic tutorial that covered the fundamentals of Adobe Experience Manager (AEM) Headless and GraphQL. Headless and AEM; Headless Journeys. This article builds on these so you understand how to author your own content for your AEM headless project. Explore tutorials by API, framework and example applications. One of these powerful features is API. By its very design, AEM leverages traditional CMS advantages. What is Headless CMS CMS consist of Head and Body. It is a Web Content Management System that allows companies to manage their web content (Web pages, digital assets, forms, etc) and also create digital experiences with this content on any platform web, mobile or IoT. Hybrid. Learn how to use Content Fragments in Adobe Experience Manager (AEM) as a Cloud Service with the AEM GraphQL API for headless content delivery. Adobe Experience Manager Sites is an industry-leading headless content management system (CMS), which makes it easy for your marketing and IT teams to create and deliver personalized content experiences — wherever. 3 and has improved since then, it mainly consists of the following components: 1. At the beginning of the AEM Headless Content Author Journey the Introduction covered the basic concepts and terminology relevant to authoring for headless. The value of Adobe Experience Manager headless. 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. Competitors and Alternatives. A headless CMS exposes content through well-defined HTTP APIs. I'd like to know if anyone has links/could point me in the direction to get more information on the following -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. AEM is considered a Hybrid CMS. AEM Headless is a CMS solution from Experience Manager that allows structured content (Content. The latter makes it easier to deliver content on various channels. The AEM Headless Client for JavaScript is used to execute the GraphQL persisted queries that power the app. API Reference. Adobe Experience Manager is super-compatible with Adobe Commerce (earlier Magento) and Adobe Commerce Cloud. Headful and Headless in AEM; Headless Experience Management. Yes it can, Headless CMS's provide enough metadata (ID's Slugs etc. In this part of the AEM Headless Content Architect Journey, you can learn the (basic) concepts and terminology necessary to understand content modeling when using Adobe Experience Manager (AEM) as a Cloud Service as a Headless CMS. Headless AEM offers organizations the flexibility to deliver content in a decoupled manner, separating the content management system (CMS) from the presentation layer. AEM projects can be implemented in a headful and headless model, but the choice is not binary. 8) Headless CMS Capabilities. That is, they can expose their content via REST APIs and other means, and we don’t have to do templating within the CMS itself. As a Headless CMS, AEM has been a success for us, and I would like to share our experiences through this article. A headless CMS is a content management system (like a database for your content). 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. Customers' Choice 2023. A headless CMS is a content management system that separates where content is stored (the “body”) from where it is presented (the “head“). At least 3 years’ content management experience, including at least 1 year using AEM, headless and headful. Browse the following tutorials based on the technology used. 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. Production Pipelines: Product functional. Authoring for AEM Headless - An Introduction. Headless CMS. " GitHub is where people build software. Use GraphQL schema provided by: use the drop-down list to select the required configuration. io. Write flexible and fast queries to deliver your content seamlessly. Contentful), frontend architectures. The headless content management system that helps you deliver exceptional experiences everywhere. The frontend, which is developed and maintained independently, fetches. 5 million in 2019. Getting Started with AEM's SPA Editor. The Story So Far. 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 to model your content as AEM Content Models; How to access your content via AEM delivery APIs; How to update your content via AEM Assets APIs; How. Last update: 2023-09-26. Using this path you (or your app) can: receive the responses (to your GraphQL queries). I'm looking for specific HTTP RESTful API documentation for AEM Assets headless-CMS. 3, Adobe has fully delivered its content-as-a-service (CaaS. AEM offers a wide range of advantages for businesses looking to streamline their content creation, management, and publishing workflows: Flexible content delivery. AEM enables headless delivery of immersive and optimized media to. It includes blog posts, eBooks, press releases, guides, and so on for websites, mobile applications, portals,. A headless CMS remains with an interface to add content and a RESTful API (JSON, XML) to deliver content wherever you need it. Get a free trial Explore Headless CMS features. In terms of. In this optional continuation of the AEM Headless Developer Journey, you learn how AEM can combine headless delivery with traditional full-stack CMS features. They can author content in AEM and distribute it to various front-end… of the application. ’. Translating Headless Content in AEM. Using AEM as a Hybrid CMS. Tap or click the folder that was made by creating your configuration. Separating the frontend from the backend unlocks your content, making it easier for marketers to manage content independently, and for developers to build faster, automate changes, and manage digital. A hybrid CMS is a “halfway” solution. This is time saving for both marketers and developers. Clients can send an HTTP GET request with the query name to execute it. AEM is a secure and reliable CMS platform that offers total privacy and protection of your business’s vulnerable data. 2. Es eignet sich, um Content für verschiedene Kanäle zentral zu verwalten; etwa für Website, Apps, Online-Shops und POS-Systeme. The. 4. Headless is an example of decoupling your content from its presentation. According to marketing experts, the Adobe Experience Manager Headless Content Management System is the future of content delivery. Headless CMS from Adobe supports developers and marketers to easily create and deliver channel-agnostic content to any end-point. Use Adobe Experience Manager as a hybrid headless CMS. Content Fragments: Allows the user to add and. 3 is the upgraded release to the Adobe Experience. 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 concepts of headless content delivery. If auth param is a string, it's treated as a Bearer token. In a headless setup, the presentation system (the head) is decoupled from the content management (the tail). Adobe Experience Manager (AEM) has grown exponentially in importance since its inception, becoming a top-tier solution for content management and digital asset management. Experience League. 5 and Headless. Tap the ellipsis next to the environment in the Environments section, and select Developer Console. This architecture diagram shows various components of a headless and conventional CMS. With GraphQL for Content Fragments available for Adobe Experience Manager 6. Read More. The AEM Headless Client for JavaScript is used to execute the GraphQL persisted queries that power the app. Topics: Content Fragments. Following is a list of some great advantages of AEM CMS CQ5 over another CMS: One of the biggest advantages of AEM CQ5 over another CMS (Content Management System) is its integration with other products from Adobe and with the Adobe Marketing Cloud. Enable developers to add automation. With Contentstack and Adobe DAM, you can take your user's experience to the next level. The main idea behind a headless CMS is to decouple the frontend from the backend and serve content to the frontend. In this part of the AEM Headless Content Architect Journey, you can learn the (basic) concepts and terminology necessary to understand content modeling for headless content delivery with Adobe Experience Manager (AEM). Community Edition. 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 is the recommended. From a traditional point of view there’s a site, screens, and a SPA editor, which gives the author in-context end-to-end control of what the end user is going to see. I'm looking for specific HTTP RESTful API documentation for AEM Assets headless-CMS. Headless CMS Adobe Experience Manager Sites provides the most innovation-friendly content delivery tools in the market, enabling you to use and reuse content across web, mobile and emerging channels — including those that have yet to be developed. Since it acquired Magento, Adobe has focused on tightly integrating the CMS (AEM) and the eCommerce arm (Adobe Commerce) to. Length: 34 min. For you devs we've created a minimal demo project and a tutorial. Can Adobe Experience Manager support headless use cases? Experience Manager is a hybrid CMS, giving you the flexibility to be used as a decoupled CMS or headless-only CMS. Conclusion. It comes with a powerful yet easy-to-use user interface that makes uploading, editing, and managing content easy. In a bid to create the perfect, composable tech stack, headless implementations can end up as elaborate exercises that require connecting multiple teams, tools, and technologies. GraphQL, an industry standard, application-agnostic query language to retrieve content, lets developers get exactly the content they need —. However, Experience Manager is best used with a hybrid approach that supports channel-centric content management and provides headless CMS functionality at the same time. This journey provides you with all the information you need to develop. And you can learn how the whole thing works in about an hour and a half. Solutions. 3 and has improved since then, it mainly consists of the following components: Content Services: Expose user defined content through an API in JSON format. compatible with. Repeat the above steps to create a fragment representing Alison Smith:To keep customers engaged, marketers and developers need to work together to quickly build and test experiences that make the most of modern app and headless technologies. See Wikipedia. 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. When using AEM Headless Persisted Queries which access AEM over HTTP GET, a Referrer Filter. Visual Copilot Livestream | Dec 6 @10am PST. A headless content management system (CMS) is a content repository that allows you to deliver content to any frontend or UI. Both AEM and Adobe Commerce are a part of Adobe’s Experience Cloud offering. In our complete guide, we are going to answer the most common questions, such as What is the difference between Headless and traditional CMS? AEM is a fully capable headless CMS that can deliver content to any device or screen with modern technologies and standards (JSON API, GraphQL etc) which should be able to scale to large user bases due to performance optimisations by Adobe. And the demo project is a great base for doing a PoC. 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. An end-to-end tutorial illustrating how to build-out and expose content using AEM Headless. And. View all features. Cockpit. 5 billion by 2026. For headless, your content can be authored as Content Fragments. Because headless uses a channel-agnostic method of delivery, it isn’t tied. 2. A Headless Content Management System (CMS) is: "A headless content management system, or headless CMS, is a back-end only content management system (CMS) built from the ground up as a content repository that makes content accessible via an API for display on any device. Create Content Fragments based on the. Next page. A popup will open, click on “ Copy ” to copy the content. The power of AEM allows it to deliver content either headlessly, full-stack, or in both. API-driven approach facilitates content delivery across multiple channels. A headless CMS is therefore responsible for the (backend) content management services, together with the mechanisms allowing the (frontend) applications to access that content. 5. The diagram above depicts this common deployment pattern. Persisted queries are queries that are stored on the Adobe Experience Manager (AEM) server. Mutable versus Immutable Areas of the Repository. AEM Headless CMS Developer Journey. Headless CMS: In Headless CMS architecture, there is no predetermined frontend which relies on templates for content presentation. This document. e. They can continue using AEM's robust authoring environment with familiar tools, workflows. ·. Contribute to adobe/aem-headless-client-nodejs development by creating an account on GitHub. On the other hand, headless CMS separates the front end from the back end and stores content separately. The headless CMS extension for AEM was introduced with version 6. Adobe Experience Manager (AEM): On the other hand, AEM offers both headless and hybrid architecture options. It is a. See Wikipedia. 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. Formerly referred to as the Uberjar; Javadoc Jar - The. . This approach also allows for easier content and resource sharing. Adobe Experience Manager Sites is an industry-leading headless content management system (CMS), which makes it easy for your marketing and IT teams to. A Content Management Systems (CMS) is foundational digital software that provides tools to manage and deliver content on a website or an application. To allow developers to easily fuel content into multiple touchpoints, we are introducing GraphQL APIs for headless content delivery. Made. It is a traditional, monolithic CMS with a content-as-a-service (CaaS) API. Virtual Event - AEM GEMs feature two of our customers presenting a technical deep dive session on the usage of AEM as Headless. 5 Star 44%. In simpler words, the headless CMS separates the content from the presentation layer and allows you to manage content using APIs. 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. AEM is a headless CMS that enables developers to easily manage and publish content across multiple channels. To associate your repository with the headless-cms topic, visit your repo's landing page and select "manage topics. It separates information and presentation. An Introduction to AEM as a Headless CMS; AEM Headless tutorials - If you prefer to learn by doing and are technically inclined, take our hands-on tutorials organized by API and framework, that explore creating and using applications built on AEM Headless. This CMS approach helps you scale efficiently to. AEM - A comprehensive content management solution for building websites . Umbraco is an excellent CMS (Content Management System) that helps you to build interactive and responsive websites. Headless CMS Adobe Experience Manager Sites provides the most innovation-friendly content delivery tools in the market, enabling you to use and reuse content across web, mobile and emerging channels — including those that have yet to be developed. The sites and web applications built using Umbraco are responsive and thus adjusts accordingly on desktops as well as smart phones. These are self-contained items of content that can be directly accessed by a range of applications, as they have a predefined structure, based on Content Fragment Models. Authorization. We're trying to integrate AEM with a CMS too. Headless implementations enable delivery of experiences across platforms and channels at scale. " Going headless can offer several advantages over a traditional. Select Create. Persisted queries are queries that are stored on the Adobe Experience Manager (AEM) server. If auth param is a string, it's treated as a Bearer token. ADOBE Experience Manager Meet the headless CMS that powers connected experiences everywhere, faster. When. Wind gusts drove biting rain into the cheeks of determined spectators. With these operations the API lets you operate Adobe Experience Manager as a Cloud Service as a headless CMS (Content Management. Objective. Clients can send an HTTP GET request with the query name to execute it. The GraphiQL tool also enables users to persist or save queries to be used by client applications in a production setting. An end-to-end tutorial illustrating how to build-out and expose content using AEM and consumed by a native mobile app, in a headless CMS scenario. A headless CMS may also be referred to as a “low-code” solution if it includes a repository or marketplace of reusable plugins and components, as they abstract away some of the complexity while speeding up application development. Adobe Experience Manager is super-compatible with Adobe Commerce (earlier Magento) and Adobe Commerce Cloud. g. Content Models are structured representation of content. Learn about the concepts and mechanics of authoring content for your Headless CMS using Content. In the download dialog box, select the download options that you want. The term “headless” comes from the concept of chopping the “head” (the front end, i. Scheduler was put in place to sync the data updates between third party API and Content fragments. You need to create personalized, interactive digital experiences. In detail, the most common and popular implementation of the SaaS CMS concept is represented by headless CMSs. Due to this approach, a headless CMS does not. 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. Adobe Experience Manager is reportedly expensive, but the company does not reveal its pricing online. From the AEM Start Screen, tap Content Fragments to open up the Content Fragments UI. Benefits of AEM Headless CMS from a Marketing Perspective. This session will cover the following - Content services via exporter/servlets Content fragment via asset API (demo) Content fragment via Graphql (demo) Some real. The power of AEM allows it to deliver content either headlessly, full-stack, or in both. This approach enables the CMS to live up to the promise of managing content in place and publishing anywhere. A Headless Content Management System (CMS) is: "A headless content management system, or headless CMS, is a back-end only content management system (CMS) built from the ground up as a content repository that makes content accessible via an API for display on any device. Provides important information about the latest release of AEM, including what’s new, supported platforms, deprecated and removed features, and known issues. 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. Using the GraphQL API in AEM enables the efficient delivery. granite. Implementing Applications for AEM as a Cloud Service; Using Cloud Manager. 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. Traditional CMS platforms hold content in predefined web templates that blend content presentation with back-end structure. 4. With Adobe Experience Manager version 6. Why would you need a headless CMS? IT is looking to address Agility and Flexibil. While decoupled from the back end, a hybrid CMS includes a presentation layer similar to a traditional or coupled CMS at the same time using a headless architecture for delivery. This is becoming more popular, and some of the renowned sites developing headless sites at the moment are adopting these. These were not the conditions in which to do the impossible. Content authors can use its intuitive interface to create content, and developers can deliver it seamlessly across channels. Headless CMSs are frontend agnostic and API-driven by design. But it’s no secret that Magento’s built-in CMS doesn’t go far when your business scales. (DXP) with a robust CMS component is Adobe Experience Manager (AEM). 5. Enter a name for the connector and also select the “CMS Source” as AEMExamples can be found in the WKND Reference Site. Moving forward, AEM is planning to invest in the AEM GraphQL API. These tests are maintained by Adobe and are intended to prevent changes to custom application code from being deployed if it breaks core functionality. Get ready for Adobe Summit. Consistency across channels Quicker content delivery More content control for marketers Future ready experiences Easier to gain buy in from marketing How does it di˚er from a traditional CMS? Headless CMS is a back end only content. It allows enterprises to offer more innovative and comprehensive customer experiences, faster and better. 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. js. Below we will compare these two types of solutions according to 5 parameters. JANUARY 2019 | The hybrid architecture of Adobe Experience Manager 5 Headless CMS architecture The term headless originates from the idea that the front-end presentation layer is the “head” of the application. CMS consist of Head and Body. The Story So Far. While traditional CMSs usually create restrictive specifications when writing content in order to standardize publishing, this is not the case with headless CMSs. These remote queries may require authenticated API access to secure headless content. 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. Get to know how to organize your headless content and how AEM’s translation tools work. The two only interact through API calls. AEM Headless APIs allow accessing AEM. 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. An introduction to the headless features of Adobe Experience Manager, and how to author content for your project. What Makes AEM Headless CMS Special. supports headless CMS scenarios where external client applications render experiences using content managed in AEM. Learn more about headless CMS. The AEM SDK is used to build and deploy custom code. Contributing. Components that both creators and developers can use. It is a query language API. Adobe AEM Magento Integration: A Tandem of CMS and Ecommerce.