Expand my Community achievements bar.

Learn about Edge Delivery Services in upcoming GEM session
SOLVED

AEM Core Components compatibility with Static templates.

Avatar

Level 1

Hi All,

I've been going through the documentation for AEM Core Components and have come across a statement that "Core Components require AEM 6.4 or higher and require the use of editable templates. They do not work with the Classic UI nor with static templates."

Is there any specific reason behind why the core components don't work with static templates?

Another question that I had was that why do we need to create proxy components from the Core components instead of directly using the given core components?

 

Thanks in advance.

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi, 


Here are some of my thoughts:

 1. Is there any specific reason behind why the core components don't work with static templates?

Yes, the static templates are deprecated, as you know. The editable templates have introduced the concept of 'policies,' which are one of the key foundations on which the core components are built. Editable templates allow authors to configure the layout and behavior of pages within the AEM Sites interface.

 

2.  why do we need to create proxy components from the Core components instead of directly using the given core components?

This is a best practice, here are the reasons why is a best practice:

  • Separation of Concerns: Proxy components act as an abstraction layer between the Core Components and your project-specific components. This separation allows you to insulate your project from changes or updates to Core Components. If Core Components change or are updated, your proxy components can remain stable, reducing the risk of breaking your website.

  • Customization: Proxy components provide a place to add any project-specific logic or adaptations that are not present in the Core Components. This allows you to extend and customize the behavior of Core Components without modifying them directly.

  • Versioning and Upgradability: By using proxy components, you can manage versioning more effectively. When you update AEM Core Components, you can test and adapt your proxy components as needed, ensuring a smooth upgrade process.

  • Consistency: Proxy components can enforce consistent usage of Core Components across your project. You can define naming conventions, default configurations, and other standards for how Core Components are used within your project.

 

Hope this helps.



Esteban Bustamante

View solution in original post

2 Replies

Avatar

Community Advisor

@malhotra_h core components uses responsivegrid as its base component to render pages which is available in editable templates, whereas static templates rely on parsys or iparsys so they are not compatible with them.

 

Proxy of component is component architecture, where we treat ootb core components as base components and proxy we create in our project folders are as site specific components, so that we can have n number of versions of components for a single base core component and within sites we can extend them to customize to site specific needs.

Avatar

Correct answer by
Community Advisor

Hi, 


Here are some of my thoughts:

 1. Is there any specific reason behind why the core components don't work with static templates?

Yes, the static templates are deprecated, as you know. The editable templates have introduced the concept of 'policies,' which are one of the key foundations on which the core components are built. Editable templates allow authors to configure the layout and behavior of pages within the AEM Sites interface.

 

2.  why do we need to create proxy components from the Core components instead of directly using the given core components?

This is a best practice, here are the reasons why is a best practice:

  • Separation of Concerns: Proxy components act as an abstraction layer between the Core Components and your project-specific components. This separation allows you to insulate your project from changes or updates to Core Components. If Core Components change or are updated, your proxy components can remain stable, reducing the risk of breaking your website.

  • Customization: Proxy components provide a place to add any project-specific logic or adaptations that are not present in the Core Components. This allows you to extend and customize the behavior of Core Components without modifying them directly.

  • Versioning and Upgradability: By using proxy components, you can manage versioning more effectively. When you update AEM Core Components, you can test and adapt your proxy components as needed, ensuring a smooth upgrade process.

  • Consistency: Proxy components can enforce consistent usage of Core Components across your project. You can define naming conventions, default configurations, and other standards for how Core Components are used within your project.

 

Hope this helps.



Esteban Bustamante