- Mobile User Guide overview
- Introduction to AEM Mobile
- Authoring On-Demand Services App
- Developing On-Demand Services App
- AEM Mobile On-Demand
- App Templates and Components
- Content Properties and Nodes
- Creating Shared Resources Export Configuration
- Creating and Adding Templates and Components
- Best Practices
- Creating Article Export Configuration
- Mobile with Content Sync
- Page Templates for Mobile Apps
- Using Content Properties to Export Content
- Rendering and Delivery
- Content Services
- Content Delivery
- Administering On-Demand Services App
- Authoring Adobe PhoneGap Enterprise
- Developing Adobe PhoneGap Enterprise
- PhoneGap
- Building Mobile Applications
- Push Notifications
- Developing Mobile Applications in AEM
- Mobile with Content Sync
- The Anatomy of an App
- Developing Apps with PhoneGap CLI
- Out of the Box App Handlers
- Creating and Editing Apps Using the Apps Console
- Is your hybrid app ready for AEM Mobile?
- Access Device Features
- Add Adobe Analytics to your Mobile Application
- Page Templates for Mobile Apps
- Configuring Adobe Target Cloud Service
- Single Page Applications
- Models in Repository
- Starting AEM PhoneGap
- Testing Mobile Apps
- Structure an App
- Track App Performance with Adobe Mobile Analytics
- Administering Adobe PhoneGap Enterprise
Rendering and Delivery
Adobe recommends using the SPA Editor for projects that require single page application framework-based client-side rendering (for example, React). Learn more.
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 renders 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
Use <RESOURCE.caas[.<EXPORT-CONFIG][.<DEPTH-INT>].json to request JSON.
| RESOURCE | an entity resource under /content/entities or a content resource under /content |
| EXPORT-CONFIG | OPTIONAL an export configuration found under /apps/mobileapps/caas/exportConfigs/EXPORT-CONFIG |
| DEPTH-INT | OPTIONAL depth recursion for rendering of children as used in Sling rendering |
Creating Export Configs
Export configs can be created to customize JSON rendering.
You can create a configuration node under /apps/mobileapps/caas/exportConfigs.
| Node Name | Name of the configuration (for rendering selector) |
|---|---|
| jcr:primaryType | nt:unstructured |
The following table shows the properties of Export Configs:
| Name | Type | Default (if, not set) | Value | Description |
| includeComponents | String[] | include everything | sling:resourceType | exclude details for nodes with specified sling:resourceType from JSON export |
| excludeComponents | String[] | exclude nothing | sling:resourceType | include details only for nodes with specified sling:resourceType from JSON export |
| excludePropertyPrefixes | String[] | exclude nothing | Property prefixes | exclude properties that start with specified prefixes from JSON export |
| excludeProperties | String[] | exclude nothing | Property names | exclude specified properties from JSON export |
| includeProperties | String[] | include everything | Property names | if excludePropertyPrefixes set else (exclude properties ignored) only include these properties |
| includeChildren | String[] | include everything | child names | exclude specified children from JSON export |
| excludeChildren | String[] |
exclude nothing | child names | include only specified children from JSON export, exclude other |
| renameProperties | String[] |
rename nothing | <actual_property_name>,<replacement_property_name> | rename properties using replacements |
Resource type export overrides
Create a configuration node under /apps/mobileapps/caas/exportConfigs.
| name | resourceTypeOverrides |
|---|---|
| jcr:primaryType | nt:unstructured |
The following table shows the properties:
| Name | Type | Default (if, not set) | Value | Description |
| <SELECTOR_TO_INC> | String[] | - | sling:resourceType | For the following sling resource types, don't return the default CaaS json export. Return a customer json export by rendering the resource as; <RESOURCE>.<SELECTOR_TO_INC>.json |
Existing Content Services Export Configs
Content Services include two export configurations:
- default (no config specified)
- page (to render site pages)
Default Export Configuration
Content Services default export configuration is applied if a config is specified in the requested URI.
<RESOURCE>.caas[.<DEPTH-INT>].json
| Name | Value |
| excludeProperties | |
| excludePropertyPrefixes | jcr:,sling:,cq:,oak:,pge- |
| includeProperties | jcr:text,text jcr:title,title jcr:description,description jcr:lastModified,lastModified cq:tags,tags cq:lastModified,lastModified |
| includeComponents | |
| excludeComponents | |
| includeChildren | |
| excludeChildren | |
| Sling JSON Overrides | foundation/components/image wcm/foundation/components/image mobileapps/caas/components/data/contentReference mobileapps/caas/components/data/assetlist |
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
See the resources below to learn about additional topics in Content Services:
Business.Adobe.com resources
Resources
Adobe Account
