Magnolia 5.5 reached end of life on November 15, 2019. This branch is no longer supported, see End-of-life policy.
...
| required Renderer to use. Magnolia supports If you have the Site module you can set You can also create a custom renderer. | ||||
| required Path to the template script as | ||||
| optional Dialog definition ID in The ID has two parts, separated by a colon:
| ||||
i18nBasename | optional Message bundle such as | ||||
title | optional Title of the template displayed to editors. The value can be literal or retrieved from a message bundle (which is defined in i18nBasename) with a key. Use alphanumeric characters in literal values. Displayed in:
| ||||
description | optional Template description displayed to editors. The value can be literal or retrieved from the message bundle (specified by | ||||
| optional The fully-qualified class name for the Java bean representing the definition data of this item. The default class is
Only set the value when using custom definition class. Example: | ||||
| optional A model class that contains business logic for the template. The model class needs to implement the
modelClass . Current content, definition and the parent model are passed to the constructor. This object is instantiated for each rendering of a page or component.A Groovy model class can be referenced from a YAML template definition. Current limitations:
Value:
| ||||
parameters | optional Custom template properties that you can access from a script without having to write a class. | ||||
| optional, in JCR node configuration only Inherits the configuration from another template definition. The value is a valid Magnolia path. See Reusing configuration. | ||||
| optional Merges template definition with the variation having the same name of the channel - if available. |
...