Magnolia 4.5 reached end of life on June 30, 2016. This branch is no longer supported, see End-of-life policy.
Dialogs are used for content entry. Editors type content into the input fields and the dialog stores it in the repository. Dialogs can be used to edit page, area and component content. The functionality of each field in a dialog is provided by a control that allows the editor to perform a task such as enter text, upload an image, select a date etc. Controls are assembled into tabs and tabs into dialogs.
The STK dialog definitions are configured in Templating Kit > Dialog Definitions. The definitions are arranged in four folders:
The STK dialogs are standard Magnolia dialogs. For more information on dialogs and how to configure them see and Controls in our Reference section.
To minimize configuration generic dialogs, tabs and fields are configured in the
/generic folder. These configurations are used over and over in the page and component dialogs. This arrangement allows you to simply reference the generic configuration instead of duplicating it. The names of the four child folders,
/master, indicate the contents of the folders and where the configuration is most used. The extends mechanism is used extensively.
Here's an example of how it works:
hideTeaserImagefield is configured in the
baseTeaserInternaldialog configured in the
/generic/masterfolder includes the two tabs used in all internal teasers:
hideTeaserImagefield is included in the first tab using the
stkTeaserdialog configured in the
extendsthe master configuration.
stkTeaser dialog that editors see.
/pages folder contains the dialog definitions used by the page templates and there is a child folder for each template. You will find the following dialog definitions for all page templates except
<template name>Propertiesfor the entry of page properties.
<template name>Introfor content entry in the Page Header component that renders in the
main/introarea on most templates. See i for more information.
/home folder has only a
stkHomeProperties dialog because the
intro area is disabled on the
stkHome template. See for more information.
There are two other exceptions in the
stkSectionHeaderdialog is used for content entry in the Section Header component in the
stkSectiontemplate. See for more information.
stkFooterdialog is used for entry of
copyrightinformation in the main footer component . See f for more information.
Each page has a properties dialog that is:
stkHomethat also includes site-wide information. The dialog allows for:
tabMain: Exclusion of the page from the navigation bars, and browser window and navigation titles that are different from the page title. See h and for how this content is used.
tabMetaData: Entry of meta keywords and description. These are inserted into the HTML by the
htmlHeader.ftlscript. See for more information.
tabChannels: Exclusion of the page from rendering in a variation, for example the
smartphonevariation. See Targeting specific content for more information.
tabDependencies: Automatically renders a list of dependent pages and DMS assets. This functionality relies on the module and is an EE feature.
The master configuration is in Dialog Defintions >
The individual dialogs are in
/<page folder>/<template name>Properties.
Here's the dialog that editors see.
All templates except
stkRedirect have a Page Header component located in the
The intro dialogs differ from template to template and are in Dialog Definitions >
/pages/<page folder>/<template name>Intro. These dialogs:
introof the page template definition.
stkArticleIntrodialog includes content and the
stkEventIntrodialog includes event-specific fields such as
imagecontent entered in the intro dialog.
Here's the definition for the
Here's the dialog the editor sees.
The component dialogs are configured in Dialog Definitions >
/components. The dialog definitions are arranged in child folders by component type. The folder and dialog definition names correspond with those of the configured in Templates Definitions >
/components. Each component definition references a corresponding dialog definition in the
dialog property node. Each dialog definition is unique and caters for content fields appropriate for the corresponding component.