Rendering and Delivery rendering-and-delivery
Adobe Experience Manager (AEM) content can easily be rendered by way of Sling Default Servlets to render JSON and other formats.
Those out-of-the-box renderings typically walk the repository and return content as is.
AEM, by way of Sling, also supports developing and deploying custom sling renderers to take full control of the rendered schema and content.
Content Services Default Renderers fill the gap between out-of-the-box Sling Defaults and Custom Development allowing customization and control of many aspects of the rendered content without development.
The following diagram shows the rendering of content services.
Requesting JSON requesting-json
Use <RESOURCE.caas[.<EXPORT-CONFIG][.<DEPTH-INT>].json to request JSON.
Creating Export Configs creating-export-configs
Export configs can be created to customize JSON rendering.
You can create a configuration node under /apps/mobileapps/caas/exportConfigs.
The following table shows the properties of Export Configs:
Resource type export overrides resource-type-export-overrides
Create a configuration node under /apps/mobileapps/caas/exportConfigs.
The following table shows the properties:
Existing Content Services Export Configs existing-content-services-export-configs
Content Services include two export configurations:
- default (no config specified)
- page (to render site pages)
Default Export Configuration default-export-configuration
Content Services default export configuration is applied if a config is specified in the requested URI.
<RESOURCE>.caas[.<DEPTH-INT>].json
Page Export Configuration page-export-configuration
This configuration extends the default to include grouping children under a child node.
<SITE_PAGE>.caas.page[.<DEPTH-INT>].json
Additional Resources additional-resources
See the resources below to learn about additional topics in Content Services: