#Adobe Experience Manager

What Are Considered Templates in AEM?

Contents

Short Answer

In Adobe Experience Manager (AEM), templates are pre-defined structures that dictate the layout and initial content of pages created within the platform.

Understanding AEM Templates

The Role of Templates in AEM

Templates in AEM serve as the foundation for creating pages. They define the page structure, components, and their configuration, ensuring consistency across the content of a website.

Types of Templates in AEM

AEM offers two main types of templates:

  1. Static Templates: Defined by developers in the JCR (Java Content Repository) and less flexible, requiring developer intervention to update.
  2. Editable Templates: Introduced in AEM 6.2, they provide authors with more control to create and manage page templates through the template editor.

Static Templates

Characteristics of Static Templates

Static templates are the traditional way of creating templates in earlier versions of AEM. They are:

  • Less flexible after creation.
  • Defined by developers.
  • Stored under the /apps directory in the repository.

Creating a Static Template

  1. Develop the Template Structure: Developers write the HTML structure and include components using JSP or HTL.
  2. Define the Content: They specify the initial content and design for pages.
  3. Deploy the Template: The template is deployed to the AEM instance.

Editable Templates

Advantages of Editable Templates

Editable templates introduced a more flexible and user-friendly approach:

  • They can be created and edited by content authors without coding.
  • Allow for controlled changes through template policies and permissions.

Creating an Editable Template

  1. Access the Template Console: Templates are managed through AEM’s Template Console, usually found at /libs/wcm/core/content/sites/templates.html.
  2. Create the Template: Authors initialize a new template with a basic structure.
  3. Edit the Template: Using the template editor, authors can add and configure components.
  4. Set Policies: Authors define component policies to control the behaviour and style of components within the template.
  5. Enable the Template: Once finalized, the template is enabled for use by content authors to create pages.

Conclusion

Templates are a core concept in AEM, critical for defining the layout and initial setup of pages. They provide a starting point for authors and ensure consistency across the site’s content. Whether using static or editable templates, AEM offers solutions to cater to both developer and content author needs, balancing flexibility, control, and ease of use.

Back to Glossary

Axamit Blog

Get Inside Scoop on Adobe Experience Manager Updates, Trends, Best Practices
September 6, 2024

Optimizing Adobe Experience Manager Performance: Expert Techniques for Peak Results

Discover actionable techniques to boost Adobe Experience Manager performance and ensure a seamless experience for your users.

Read More
AEM Migration from Your Current CMS
July 9, 2024

Conquering AEM Migration: Shift Seamlessly From Your CMS to Adobe Experience Manager

Discover the core CMS issues that lead enterprises to upgrade to AEM and build your foundation around the migration process as a whole.

Read More
Future-Proof Your Content Authoring with a Component Content Management System
June 7, 2024

Future-Proof Your Content Authoring with a Component Content Management System

You could be leaving untapped ROI on the table with a standard CMS. But a CCMS can fix that, and we’ll explain how.

Read More