The information here is focused on the Content Fragment Core Component, as available in the Content Fragment Updates and Content Services Feature Pack and its dependencies.
However, the functionality is available for all components in release 1.1.0 of the Core Components.
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:
- Single Page Applications
- Native Mobile Applications
- 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.
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.
Within AEM the delivery is achieved using the suffix
You can alternatively deliver the contents of a structured content fragment by targeting it specifically.
This is done using the entire path to the fragment (via the jcr:content); for example with a suffix such as.
Your page can contain either a single content fragment or multiple components of various types. You can also use mechanisms such as list components to automatically search for relevant content.
You can adapt your own components to access and use this data.
- Assets HTTP API
- Sling Models:
- AEM with JSON: