Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn more

View all

Sign in to view all badges

SOLVED

Editable Template Clientlibs

Sh1ju
Level 4
Level 4

Hi,

Instead of using sling:resourceSuperType 'core/wcm/components/page/v2/page' ,I want to use a custom page component.So what are the OTB clientlibs required to include in my custom page component to achieve a layout like this (Check the screenshot)

Editable TemplateEditable Template

Editable templates
1 Accepted Solution
Vijayalakshmi_S
Correct answer by
Community Advisor
Community Advisor

Hi @Sh1ju,

Could you please explain about the custom page component that you are referring to.

Is it completely created from scratch without inheriting from Core V2 or from wcm/foundation/components

 

 

View solution in original post

6 Replies
Vijayalakshmi_S
Correct answer by
Community Advisor
Community Advisor

Hi @Sh1ju,

Could you please explain about the custom page component that you are referring to.

Is it completely created from scratch without inheriting from Core V2 or from wcm/foundation/components

 

 

View solution in original post

Sh1ju
Level 4
Level 4

Hi @Vijayalakshmi_S 

Yes,it is completely created from scratch without inheriting core v2 or wcm foundation components

Vijayalakshmi_S
Community Advisor
Community Advisor

Hi @Sh1ju,

Guess you have marked answer correct by mistake.

Could you please explain if there is any specific reason for not making use of it (core v2 or from wcm). 

On a high level, could guess should be quite a lot of files associated to it without making use of any of the two. However while check in parallel from my end while you reply.

Sh1ju
Level 4
Level 4
Hi @Vijayalakshmi_S , I have lot of custom files associated with my custom page component
Vijayalakshmi_S
Community Advisor
Community Advisor

Hi @Sh1ju,

You can have custom files while still making use of core page component. 

In older version of AEM, it was a practice to inherit from foundation components. Now with latest version it is recommended to inherit from Core components though we have customization to it.

I suggest you to go through the structure of core v2 page component files (how is it organized) and overwrite the one necessary to have your custom files included in the respective files. 

 

Per the lines from below link(Section Usage), this core component forms the basis of Editable templates. 

https://docs.adobe.com/content/help/en/experience-manager-core-components/using/components/page.html 

Also, we have dialog, design dialog part of core component which we need not have to do it from scratch. Even if this calls for a customization, you can make use of Sling Resource Merger - mount point concept. 

 

More than Editable templates, thinking on a long run in terms of upgrade/exposing page model as JSON/ Content services, it is better to inherit than to deal with lot of customization any further.

 

Ankur_Khare
Community Advisor
Community Advisor

Hi,

Could you please let us know the reason why you don't want to extend v2 component?

Then it would be easier to answer your query.