Skip to main content

Templates

Templates define the structure of the Page; without template we cannot create any Page. 

Template defines the Where the Iparsys and Parsys have to be added and what components should be displayed on the layout container.

Prior AEM 6.2, there were only static templates, from aem 6.3 Adobe introduced Editable Templates/Dynamic Templates.

1) Static Templates

Static Templates are created by the Developer, where content author just uses the templates and creates the Pages.  If you want to enable any components to be shown on the page then on the page needs to go to design mode and add the specific components.

In static templates by default some component needs to shown on the Page then developer needs to add the component on the template through code.

Editable Templates

From 6.3, Adobe introduced new feature of Editable templates.  The content author can create templates and can add structure, initial content, Policies. 

Editable Template contains mainly 3 features

1)      Structure : This defines the structure of the page and components included on the parsys/iparsys. Also you can add specific components on the Template, and you can restrict the author to edit the added components by lock/unlock feature on the component.

2)      Initial Content:  By default, when the page is created then what ever you add in the initial content that will be automatically added to the Page.

3)      Layout/Emulator: This defines the view of Mobile, Desktop, Tablet.

   Policies:

Policies are of 2 Types.

  • Template level Policies
  • Component Level Policies

If you want to add any new component, to be shown on the author mode then the component should be added to the template level Policies.

If you want to add any Styles to the specific component then that should be on the component level Policies.

***All the Policies are stored under /conf/project-name/settings/wcm

For more information on AEM , go through the below syllabus.

Comments

Popular posts from this blog

AEM Author Concepts

What is AEM? Author Publisher Dispatcher in AEM Touch UI vs C lass UI   DAM (Digital Asset Management) Replication/Publish in AEM Parsys/Responsivegrid/Iparsys Components Pages Templates Experience Fragments Content Fragments Emulator / Break Points RichText Tagging Sitemap Personalisation Workflows MSM(Multi Site Management) Users and Groups Environments in SDLC

What is AEM?

  AEM is full form is Adobe Experience Manager and many people call it as adobe cq5,cq5.   AEM is a web Content Management System Tool (wcms/cms), which is a used for building websites, mobile apps and forms. AEM makes easy to manage your content and assets.  By using aem, we can dynamically change the content within fraction of seconds and same can be shown in live. Examples:  News Channel websites, in news channel websites the layout (look and feel) will be same only the content changes dynamically. Other CMS Tools: WordPress,Drupal,Sitecore. For more information on AEM , go through the below syllabus. AEM Author Concepts

MSM (Multi Site Management)

 Multi Site Manager (MSM) allows aem developers to create copy of existing site and automatically update the copy when changes are done to the source site. Advantages of using MSM: Easily manage multiple websites that share common content. MSM allows aem developers to define relations between the sites so that content changes in one site are automatically replicated in all other sites. Reduces the time to manage your websites and increases the re-use of common content. Maintain common look and feel across all websites. When we should use MSM Sites are in multiple countries. Sites are in multiple languages. Need to reuse/replicate same content in multiple websites. Maintain consistent branding and content across websites. Creation of MSM from scratch (follow below) Create Language Masters Here we will create a sample English site, which will be used in the later point of creating multiple language copies. Create language-masters with any template. Create a sample site with Eng