1. No category

Creating Templates for Folio Pages
Creating Templates for Folio Pages
Overview / Adobe Experience Manager / Adobe Experience Manager 6.0 / Developing / Extending AEM Features / Extending
Publications /
Templates for Publications folios perform the same function as page templates. As with page templates, folio
templates identify a page component, a design, the permitted page location and the permittted page parent
node. Typically, you create a template for each combination of these items that is required to support your
different page layouts.
Folio templates additionally specify values for the following properties to support different types of publishingrelated entities.
Name
Type
Description
dps-resourceType
String
Identifies the type of folio. The
following values are supported:
• dps:Issue
• dps:Article
This property is required for
enabling the uploading of the
folio to Digital Publishing Suite.
dps-exportTemplate
For dps:Issue resource types,
specifies the Content Sync
template to use for exporting the
publication issue to the format
that DPS requires.
String
At a minimum, you require a template for creating publication issues and a template for creating pages that
an issue contains.
Issue Templates
Publication issues are based on cq:Page components. To define the page as a Publication issue, the
jcr:content node of your template requires the following property values:
• sling:resourceType = the path to your issue page component
• dps-resourceType = dps:Issue
The issue template also identifies the Content Sync template that is used to generate the ZIP file that is sent
to Digital Publishing Suite. The dps-exportTemplate property of the jcr:content node provides this value.
The sample /apps/geometrixx-unlimited/templates/issue template includes these properties. It also provides
default values for some of the page properties in the New Folio dialog:
Article Templates
Publication articles are based on cq:Page components. To define the page as a Publication article, the
jcr:content node of your template requires the following property values:
© 2012 Adobe Systems Incorporated.
All rights reserved.
Page 1
Created on 2014-11-12
Creating Templates for Folio Pages
• sling:resourceType = the path to your article page component
• dps-resourceType = dps:Article
You can also use the template to configure values for the dps:isAdvertisement and dps:isHiddenFromTOC
properties on the jcr:content node. The /apps/geometrixx-unlimited/templates/adpage template includes
these properties to identify advertisements and so they do not appear in the table of contents.
TEMPLATE GROUPS FOR ARTICLE TEMPLATES
You can create a group of interchangeable templates that authors can apply to articles after they have been
created. These templates enable authors to apply different page layouts or styles to the same content.
For example, you can create multiple templates that use different resource types (different
sling:resourceType properties) to establish different layouts for the page content; or, use different designs
(different cq:designPath properties) to change the presentation via CSS pages.
After an author creates a page, they can use the article's DPS Page Properties to select a different template
to use for rendering the page content. The list of templates that apper in the DPS Page Properties are those
that belong to the same Template Group as the template that the article currently uses.
NOTE
When authors change the template for a page, the existing page content is used within the
context of the new template. The templates that you include in the same group should all be
compatible with the same content.
Templates are in the same Template Group when they use the same value for the templateGroup property.
1.
2.
3.
In CRXDE Lite, select the template node, for example:
/apps/geometrixx-unlimited/templates/article
Add the following property:
• Name: templateGroup
• Type: String
• Value: The name of the template group.
Click Save All.
© 2012 Adobe Systems Incorporated.
All rights reserved.
Page 2
Created on 2014-11-12