Adobe Experience Manager is the best CSM, which is backed by OSGi, JCR, and jackrabbit like framework, which makes it advance and best CSM solution. Adobe Experience Manager gives a solution for content-oriented Web-applications.
Other technologies like Dev-ops also back it up in order to manage load balancing and provide additional security. Configuring dispatcher in aem is One of them, which gives all such kind of availability that makes it more powerful.
There is another powerful concept of Templates, ie static templates and editable templates in aem which makes it awesome. So let’s start
what is Templates in Aem
Template is like a base page on which the components are stuffed, components are basically html, css and js code.In order to create a new page, the template is used and it acts as the base of the new page. Template basically defines the structure of the page(Initial content and components that will be used).
There are basically two types of Templates in Aem:
1. Static Template
2. Editable Template
Static Templates in aem
Static templates are available for almost all of the versions of AEM. Static templates are defined and configured by developers. There is no dynamic connection between page and template. Static templates are stored under /apps folder. In static templates, design mode is available for defining properties.
Now let’s see how static templates are created:
1. Go to crx console
2. Now under your project folder i.e., present in /apps folder create a new folder naming Template, right-click on it and select Create Template option.
3. Now we will see a prompt there, fill out the following information: Label: content page
Title: My project content page
Description: The content page for Yourprojectname
Resource Type: Yourprojectname/components/page/contentpage Ranking: It defines the position of the template like 1 would mean in the first position.
4. Now click on Next, then you’ll be asked to define Allowed Paths, type /content(/.*)? in it because it is used for looking templates and click Next button.
5. Now you’ll see allowed children prompt, skip it and click on Ok and then Save All button.
Note: We can also specify Allowed Paths this way /content/Yourprojectname/en/* for a specific project.
In our next post, you will learn about editable templates in aem