This documentation is still in progress. We are working hard to update all our screenshots to the new Magnolia 6 style. Please bear with us.
Editor is a component that edits a content item. The editor typically contains a form. In a content app, you should create an editor definition under the
detail subapp. Define the node types the editor edits, a form for editing them, and actions for saving the edit.
A node type that this editor component can edit and save.
A Magnolia or JCR node type such as
CSS class that identifies an icon displayed on the items in the workbench.
Actions available in the editor. Define the actions in separate action definitions and reference them here by name.
Name of a primary action. Typically you need at least
A secondary action area in the bottom left corner of the editor. Contains the action area configuration.
For an example, see Configuring secondary actions.
Add subnodes to match the secondary actions defined in the
Name of a secondary action.
Define a subnode for each action which requires its own renderer.
Name of the secondary action.
A renderer class if the secondary action requires one. Must implement ActionRenderer .
A form definition if this editor is used to edit form-like data.
optional, default is
Click the expand/collapse button in the top right corner to toggle between the wide and normal (720px) modes.