Discover the editable templates that Adobe Experience Manager 6.2 introduces, and its powerful UI to compose and configure your pages. See how it allows to control exactly what content authors are allowed to do on the resultant pages. Understand to which extent this feature can streamline the interactions between the development and the content teams. Templates no longer have to be hand-coded and can now be maintained through a powerful UI by a new group of users: the template authors. They are in charge of maintaining the combination of components, layouts and configurations that compose a template, drastically reducing the complexity of building templates. This session is for a technical audience to learn how to enable the new template author role. It will introduce the new concepts, show how to create, edit and maintain templates through a dedicated UI, and eventually dive into the detailed aspects of its inner mechanics.

1. #evolverocks
EMPOWER TEMPLATE AUTHORS
PATRICK FAUCHERE
08/30/2016
Software Engineer

2. #evolverocks 2
ABOUT US
##
#
#
Facebook
facebook.com/adobe
Mail
fauchere@adobe.com
Twitter
twitter.com/Adobe
Linkledin
linkledin.com/company/adobe
Patrick Fauchere
Software Engineer
Adobe
Contact Us
www.adobe.com
Twitter
twitter.com/PatrickFauchere#

3. #evolverocks 3
1. Introduction and Concepts
2. Create a simple template
3. Edit template & advanced capabilities
4. Technical architecture of templates
5. Observe a custom template type
AGENDA

4. #evolverocks 4
Main capabilities:
• Compose templates out of existing components
• Control how pages using the template can be edited
• Pre-configure the design properties of the page and components
• Provide initial content to the new pages
INTRODUCTION AND CONCEPTS
TEMPLATE EDITOR

5. #evolverocks 5
Maintain hand-coded variations of templates
• Multiple variations of components
• Multiple list of allowed components
• Multiple component settings
 Moved from static files to configuration 
INTRODUCTION AND CONCEPTS
TEMPLATE EDITOR
What it solves

6. #evolverocks 6
Make use of the Configuration Manager
• Centralized location for configurations
Resource resolution strategy
• /conf
• /apps
• /libs
RESOLUTION
OF THE TEMPLATE RESOURCES

7. #evolverocks 7
A template has various states
• Draft
• Enabled
• Disabled
• Published
LIFE CYCLE
OF THE TEMPLATES

8. #evolverocks 8
The policy characteristics
• Carries the design properties
• Portable – can be located at different places
• Reusable – can be shared by multiple templates
• Provides the configuration for mapping the assets into components
DESIGN PROPERTIES
THE POLICY

9. 9
TMODULAR DESIGN
http://www.cuboro.ch/
• Content
• Component
• Template structure
• Design properties

10. #evolverocks 10
Creating a new template requires the collaboration between
Developer
• Builds components to be added to the templates and pages
Template Author
• Provides templates and configurations out of the available components
Page Author
• Creates pages and content from the available templates and components
INTRODUCTION AND CONCEPTS
ROLES

11. #evolverocks 11
The template editor terminology defines different kind of content
Locked Structure
• Content restricted to the template
Editable Structure
• Structure content set as editable on the page
Initial Content
• Content provided by the template and editable on the page
INTRODUCTION AND CONCEPTS
KIND DEFINITION

12. #evolverocks 12
TEMPLATE DEMO

13. #evolverocks 13
AR C H ITEC TU R E

14. #evolverocks 14
1
Walkthrough of
the template concepts
2
Created and used
a new template
3
Explored the technical
architecture
SUMMARY
TEMPLATE

15. #evolverocks 15
The template-type contains the initial content of a template
• Template of template
• Content structure copied over to the new template
• Pre-configured set of configuration – policies, allowed components
• No logical bond between the template type and the templates
• Created by the Developer
TEMPLATE TYPE
CHARACTERISTICS

16. #evolverocks 16
The templating mechanics detail you need to know
Policy mapping
• Structure: unique per component
• Initial Content: by component type
Policy
• Component path followed by policy node name
Root Container
• Static container required to start adding content to the template
Editable Structure Components
• Flagged as editable on the structure aspect
• Carries the properties on the initial aspect
TEMPLATE TYPE
RESOURCE LOCATION

17. #evolverocks 17
TEMPLATE TYPE DEMO

18. #evolverocks 18
1
Purpose of
the template type
2
Locate references and
resources
3
Observed the structure of
a template type
SUMMARY
TEMPLATE TYPE

19. #evolverocks 19
Useful resources
Editable Template Documentation
• https://docs.adobe.com/docs/en/aem/6-2/develop/templates/page-templates-editable.html
We.Retail Repository
• https://github.com/Adobe-Marketing-Cloud/aem-sample-we-retail
Custom Template Type Repository
• https://github.com/Adobe-Marketing-Cloud/aem-sites-example-custom-template-type
Frontend Core Editor API
• https://docs.adobe.com/docs/en/aem/6-2/develop/ref/jsdoc/ui-touch/editor-core/index.html
RESOURCES
AND REFERENCES

20. #evolverocks
THANK YOU!