Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: fix anchors phase 2

...

Localtab Group
Localtab
activetrue
titleYAML file
Code Block
languagejs
titleexample/templates/pages/home.yaml
renderType: freemarker
templateScript: /my-module/templates/pages/home.ftl
dialog: my-module:pages/homePageProperties
# areas:
visible: true
class: com.example.templates.CustomTemplateDefinition
modelClass: com.example.templates.HomePageModel
Localtab
titleJCR node
Advanced Tables - Table Plus
heading0
multiplefalse
enableHeadingAttributesfalse
enableSortingfalse
classm5-configuration-tree
enableHighlightingfalse
Node nameValue

Mgnl f
templates

 

Mgnl f
pages

 


Mgnl n
home

 

Mgnl n
areas

 


Mgnl n
<area definitions>

 


Mgnl p
class

com.example.templates.CustomTemplateDefinition

Mgnl p
dialog

my-module:pages/homePageProperties

Mgnl p
modelClass

com.example.templates.HomePageModel

Mgnl p
renderType

freemarker

Mgnl p
templateScript

/my-module/templates/pages/home.ftl

Mgnl p
visible

true

Properties specific to page template definition:

visible

optional , default is true

true makes the template available to editors.

When visible is set to false, the template is not available. However, the opposite is not always true. There are more ways to control page template availability .

type

optional, default is content

Assigns a type to the template. Types control template availability in the page hierarchy. For example type home is available at the site root level, section at level 2, and content at level 3. See Page template availability  on how to use the type property.

Info

This property is different from the type property in Area definition.

subtype

optional

Assigns a subtype to the template. You can use subtypes to aggregate content. For example, aggregate all content pages of subtype news into a teaser component. There are no default values and you can use arbitrary values to categorize your templates in any way you like.

autoPopulateFromRequest

optional,  default is true

The population of request parameters is typically enabled globally in /server/rendering/engine. Add this property and set to false to override the global setting. See Populating the rendering model with request parameters for more.

areas

optional

Area definitions.

...

Localtab Group
Localtab
activetrue
titleYAML file
Code Block
languagejs
title<module name>/templates/pages/<page template name>.yaml
areas: 
  area-1:
    # area-1 configuration
  area-2:
    #area-2 configuration 
Localtab
titleJCR node
Advanced Tables - Table Plus
heading0
multiplefalse
enableHeadingAttributesfalse
enableSortingfalse
classm5-configuration-tree
enableHighlightingfalse
Node nameValue

Mgnl n
<page template name>

 

Mgnl n
areas

 


Mgnl n
area-1

<area-1 configuration>

Mgnl n
area-2

<area-2 configuration>