Under the
cq:childEditors
node create a new node for each in-place editor:

Name: the name of each node should be the name of the property that it represents (as with drop targets). For example,
image
,
text
.

Type: cq:
ChildEditorConfig

There is a correlation between the defined drop targets and the child editors. The name of the
cq:ChildEditorConfig
node will be considered to be the drop target ID, for use as a parameter to the selected child editor. If the editable sub area does not have a drop target (e.g. as with a text component) then the name of the child editor is still considered as an ID to identify the corresponding editable area.

On each of these nodes (
cq:ChildEditorConfig
) define the properties:

Name:
type

Value: name of the registered in-place editor; for example,
image
,
text

Name:
title

Value: the title that you want to display in the components selection list (of available editors); for example,
Image
,
Text

Additional Configuration for Rich Text Editors

Configuration for multiple Rich Text Editors is slightly different as you can configure each individual RTE instance separately.

Recommended best practice is to define the
config
node under
cq:InplaceEditingConfig
as each individual RTE can have a different configuration.

However, for RTE, the
configPath
property is supported when there is only one instance of text editor (editable sub-area) in the component. This use of
configPath
is provided to support backwards compatibility with older UI dialogs of the component.