In the Experience Manager interface, group labels can serve as a visual cue that several properties are related.
Group labels are only used to provide additional context in the editing interface of Experience Manager and do not affect rendering in the front-end application. Group labels are optional.
One use of group labels is to give the content administrator information about properties that they need to configure the cartridge. For example, if a template defines properties that are required in order to render the content properly, you can indicate these with a descriptive group label so that the content administrator can easily identify the required fields in Experience Manager.
The editor panel in Experience Manager includes a default heading of
"Section settings." This heading includes the required
Name
field and the read-only
type
of a template, as well as any properties that are
defined before the first group label.
To add a group label to the editor panel:
Insert the
<GroupLabel>
element inside<BasicContentItemEditor>
as in the following example:<ContentTemplate xmlns="http://endeca.com/schema/content-template/2008" xmlns:editors="editors" xmlns:xavia="http://endeca.com/schema/xavia/2010" type="SidebarContent"> <!-- additional elements omitted from this example --> <EditorPanel> <BasicContentItemEditor> <GroupLabel label="Define Spotlight"/> <editors:StringEditor propertyName="title" label="Spotlight Title" enabled="true"/> <editors:StringEditor propertyName="maxNumRecords" label="Max Number Of Records" enabled="false"/> <editors:RecordListEditor propertyName="recordSelection" label="Spotlight Records"> <PreviewProperty name="product.name"/> </editors:RecordListEditor> <editors:StringEditor propertyName="seeAllLink" label="See All Link" enabled="true"/> </BasicContentItemEditor> </EditorPanel> </ContentTemplate>
<GroupLabel>
is an empty tag that allows you to specify the label text with thelabel
attribute.