With Content Fragments and the GraphQL API you can use Adobe Experience Manager (AEM) as a Cloud Service as a Headless Content Management System (CMS).
This is achieved using Content Fragments, together with the AEM GraphQL API (a customized implementation, based on standard GraphQL), to headlessly deliver structured content for use in your applications. The ability to customize a single API query allows you to retrieve and deliver the specific content that you want/need to render (as the response to the single API query).
GraphQL se utiliza actualmente en dos escenarios (independientes) en Adobe Experience Manager (AEM) as a Cloud Service:
A Headless Content Management System (CMS) is:
* **
In terms of authoring Content Fragments in AEM this means that:
You can use Content Fragments to author content that is not primarily intended to be directly published (1:1) on formatted pages.
The content of your Content Fragments will be structured in a predetermined manner - according to the Content Fragment Models. This simplifies access for your applications, which will further process your content.
GraphQL es:
* **
Consulte GraphQL.org
🔗 🔗 The content returned can then be used by your applications.
For Adobe Experience as a Cloud Experience, a customized implementation of the standard GraphQL API has been developed. 🔗
Fragmentos de contenido:
Contain structured content.
🔗
Provide the data types and fields required for GraphQL. They ensure that your application only requests what is possible, and receives what is expected.
Is of particular interest in conjunction with GraphQL.
Is a specific data type that can be used when defining a Content Fragment Model.
References another fragment, dependent on a specific Content Fragment Model.
Allows you to retrieve structured data.
¿Busca un tutorial práctico? Consulte el tutorial completo Introducción a AEM Headless y GraphQL, que ilustra cómo crear y exponer contenido mediante las API de GraphQL de AEM y consumido por una aplicación externa, en un escenario de CMS sin encabezado.