AEM's Editable Templates: Common ground for authors and developers | AEM Community Blog Seeding

Avatar

Avatar
Establish
Community Manager
kautuk_sahni
Community Manager

Likes

1,206 likes

Total Posts

6,421 posts

Correct reply

1,148 solutions
Top badges earned
Establish
Coach
Originator
Contributor 2
Contributor
View profile

Avatar
Establish
Community Manager
kautuk_sahni
Community Manager

Likes

1,206 likes

Total Posts

6,421 posts

Correct reply

1,148 solutions
Top badges earned
Establish
Coach
Originator
Contributor 2
Contributor
View profile
kautuk_sahni
Community Manager

24-03-2021

BlogImage.jpg

AEM's Editable Templates: Common ground for authors and developers by amplexor - Sander Lenaerts

Abstract

Editable Templates give content authors more independence from developers – If you make the best use of all features. Here's what you need to know.

The creation of templates within Adobe Experience Manager (AEM) can sometimes be a tedious and time-consuming task for developers. But it doesn't have to be: Meet Editable Templates.

The feature of Editable Templates was introduced already with the release version AEM 6.2, making it a breeze to create new and adjust existing Editable Templates on the fly. Since then, the concept has opened up the world of template creation for content authors, making it not solely a developer's task anymore.

Editable Templates have a lot of potential and can create notable value to the content management process. However, there are a few things to consider when taking the plunge towards the feature. Before we dive in, let's get you acquainted with a few basic functionalities within Editable Templates.

First of all, the concept gives you the option to define content policies. These are small snippets of configuration, where you manage what the allowed components of your template are. It's also the place to define the style variations that can be applied to the component.

The definition of style variations per component gives you flexibility and convenience: You can define multiple policies per component – and choose individually for each template which of those policies should be applied. This gives you the flexibility of allowing one set of styles on a certain component on one template, and different variations on another.

Read Full Blog

AEM's Editable Templates: Common ground for authors and developers

Q&A

Please use this thread to ask the related questions.