Templates are blueprints for creating pages, areas and components. When you add a page in the Pages app you must choose a template.
A template consists of:
Template definition | |
Template script | required A template script defines the output, typically HTML, and is interpreted by a Renderer. The script is written in a templating language such as FreeMarker. In the context of developing Single-page applications, the elements comparable to FreeMarker template scripts are components, which are compiled into a single HTML page. On the Magnolia side, the rendering of the page is handled by the SPA renderer. |
Dialog definition | optional |
Model | optional The model is a JavaBean implementing |
If developing a Single-page application, templating takes form of building Angular or ReactJS components, which are compiled into a single HTML page. On the Magnolia side, the rendering of the page is handled by the SPA renderer and the associated SPA helper libraries.
For an overview, see the Single-page applications page.
Elements of the Magnolia template mechanism:
The diagram abbreviates the field class as i.m.u.f.f.d.TextFieldDefinition
to save space. This is not a valid value. Use fully-qualified field class names such as info.magnolia.ui.form.field.TextFieldDefinition
in your definitions.
The Magnolia CLI speeds up template creation for light developers. The tool provides commands that automatically create basic template definitions and scripts on the file system.