AEM’s Content Services leverages traditional AEM Pages to compose headless REST API endpoints, and AEM Components define, or reference, the content to expose on these endpoints.
AEM Content Services allows for the same content abstractions used for authoring web pages in AEM Sites, to define the content and schemas of these HTTP APIs. The use of AEM Pages and AEM Components empowers marketers to quickly compose and update flexible JSON APIs that can power any application.
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.
This tutorial explores how AEM Content Services can be used to power the experience of an Mobile App that displays Event information (music, performance, art, etc.) that is curated by the WKND team.
This tutorial will cover the following topics:
The source code, and content packages are available on the AEM Guides - WKND Mobile GitHub Project.
If you find an issue with the tutorial or the code, please leave a GitHub issue.
|AEM GraphQL APIs||AEM Content Services|
|Schema definition||Structured Content Fragment Models||AEM Components|
|Content||Content Fragments||AEM Components|
|Content discovery||By GraphQL query||By AEM Page|
|Delivery format||GraphQL JSON||AEM ComponentExporter JSON|