- 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
App Templates and Components
Adobe recommends using the SPA Editor for projects that require single page application framework-based client-side rendering (e.g. React). Learn more.
A Template is used to create a Page and defines which components can be used within the selected scope. A template is a hierarchy of nodes that has the same structure as the page to be created, but without any actual content.
Each Template will present you with a selection of components available for use.
- Templates are built up of Components;
- Components use, and allow access to, Widgets and these are used to render the Content.
To learn how to develop your AEM application using CRXDE Lite, see Developing with CRXDE Lite.
A template is the basis of a page.
To create a page, the template must be copied (node-tree /apps/<myapp>/templates/<mytemplate>) to the corresponding position in the site-tree: this is what happens if a page is created using the Websites tab.
This copy action also gives the page its initial content (usually Top-Level Content only) and the property sling:resourceType, the path to the page component that is used to render the page (everything in the child node jcr:content).
Structure of a Template
There are two aspects to be considered:
- the structure of the template itself
- the structure of the content produced when a template is used
A Template is created under a node of type cq:Template.
Various properties can be set, in particular:
- jcr:title - title for the template; appears in the dialog when creating a page.
- jcr:description - description for the template; appears in the dialog when creating a page.
This node contains a jcr:content (cq:PageContent) node which be used as the basis for the content node of resulting pages; this references, using sling:resourceType, the component to be used for rendering the actual content of a new page.
To learn the basics for templates and components in AEM, see the resources below:
After you have the basic understanding of Templates and Components, see the following resources:
- Creating and Adding Templates and Components
- Using Content Properties to Export Content
- Best Practices
- Developing AEM Mobile Content Services
Additional Resources
To learn about additional topics on mobile apps, see the links below:
Business.Adobe.com resources
Resources
Adobe Account
