MaestroThe UI design product. + Avalon TemplateThis topic is related to the Avalon Template used in Maestro. | Template Designer | 21.11 This feature was introduced in 21.11.
A new template that you create based on the default Avalon Template has a well-defined structure. Let's examine its structure to understand how it works and how you can extend it.
When you open the new template in the Maestro editor, you should see something like this.
The standard Avalon template has pre-configured components arranged in a particular order. Components come with some elements so you can use them out of the box, or you can add, remove, modify and change the order of them as needed.
The new template can be split into the following groups:
Let's look at each groups in detail.
The main Avalon template's components and their children components are listed below:
The template has an extension point set at the root, so you may need to move it to limit the scope where content can be modified.
The Body > Content is where you may be doing most of your changes. If this is the case, it is a good idea to set the extension point there
The Avalon template comes with the following Dialogs:
Each Dialog has an extension point set at the root, so you may need to move it to limit the scope where content can be modified.
The Avalon template comes with the following Modal Pages:
Each Modal Page has an extension point set at the root, so you may need to move it to limit the scope where content can be modified.
Next, learn about template JSON definition.