
Abstract
AEM Content Services are designed to generalize the description and delivery of content in/from AEM beyond a focus on web pages.
They provide the delivery of content to channels that are not traditional AEM web pages, using standardized methods that can be consumed by any client. These channels can include:
1. Single Page Applications
2. Native Mobile Applications
3. other channels and touch-points external to AEM
With content fragments that use structured content, you can provide content services by using the JSON exporter to deliver the contents of an(y) AEM page in JSON data model format. This can then be consumed by your own applications.
JSON Exporter with Content Fragment Core Components
Using the AEM JSON exporter you can deliver the contents of an(y) AEM page in JSON data model format. This can then be consumed by your own applications.
1. Within AEM the delivery is achieved using the selector model and .json extension.
.model.json
For example, a URL such as:
http://localhost:4502/content/we-retail/language-masters/en.model.json
Read Full Blog
Q&A
Please use this thread to ask the related questions.
Kautuk Sahni