Converting static to editable templates - Page properties | Community
Skip to main content
AEMLearner-1989
AEMLearner-1989
Level 4
June 17, 2020
Solved

Converting static to editable templates - Page properties

  • June 17, 2020
  • 2 replies
  • 1644 views

Hi Team,

 

How to get initial page properties.

 

Page properties are saved under : /conf/project-name/settings/wcm/templates/template-name/initial/jcr:content

 

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by arunpatidar

Initial Content is used to create default initial content when page is created and that is store at page level.The initial content can then be edited and removed by page authors.

 

No need to worry about initial content for static to dynamic template migration but define it for the new pages based on your requirement.

 

Initial page properties should be defined under : /conf/project-name/settings/wcm/templates/my-template/initial/jcr:content

2 replies

vanegi
Adobe Employee
vanegiAdobe Employee
Adobe Employee
June 17, 2020

The best route for designing editable template is to redesign the templates directly to be the editable template. You can check the document [1] as a reference for creating editable templates.

 

We recommend to create the page templates from scratch. This is the best route and what we suggest to go with to avoid downstream issues and unintended side-effects.

 

It is advised to upgrade the templates and the general process is:

 

The basic idea is that all the components that are declared inside the static template should become a component declared as a content structure under the "structure" child node of an editable template. All synthetic resources should also become an actual node of the "structure" aspect of the template or be relocated in the HTL template or JSP page of an instanced component.

 

 

[1]:- https://docs.adobe.com/content/help/en/experience-manager-65/developing/platform/templates/page-templates-editable.html

 

arunpatidar
Community Advisor
arunpatidarCommunity AdvisorAccepted solution
Community Advisor
June 17, 2020

Initial Content is used to create default initial content when page is created and that is store at page level.The initial content can then be edited and removed by page authors.

 

No need to worry about initial content for static to dynamic template migration but define it for the new pages based on your requirement.

 

Initial page properties should be defined under : /conf/project-name/settings/wcm/templates/my-template/initial/jcr:content

Arun Patidar
arunpatidar
Community Advisor
arunpatidarCommunity Advisor
Community Advisor
June 20, 2020
Initial properties would be added automatically when you create a page, and you can access using Page API. But if page does not have properties then you you should get those properties in page. Reading directly is not advisable because initial is optional. Intentionally removing initial content from page will be available from conf. If you need same properties on all the pages then go for structure not from initial. Now come to your question - How to read initial content? you can use Node or JCR API to read any content in Java but make sure user should have access to read these nodes.
Arun Patidar
Terms & ConditionsAccessibility statement

Loading footer...