Component autogeneration
Autogeneration creates components inside an area automatically without
editor involvement. Anything you define under the content
node will
be autogenerated.
Autogeneration behavior
Autogenerated components behave differently from normal components:
-
Ordered as defined: In an empty area, components are autogenerated in the same order as they are defined in the area definition.
-
New components are placed last: If an area already has autogenerated components, newly defined components will be placed last.
-
Cannot delete permanently: When you delete an autogenerated component, it is regenerated and placed last in the area.
Autogeneration properties
Configure component autogeneration in an
area definition
under the autoGeneration
node.
areas:
footer:
renderType: freemarker
type: single
autoGeneration:
content:
quotation:
nodeType: mgnl:component
templateId: my-module:components/quotation
quotationText: <p>Carpe diem.</p>
citedPerson: Horace
references:
class: java.util.ArrayList
0: Hesperides1648
1: Marvell1681
2: Frost1938
generatorClass: info.magnolia.rendering.generator.CopyGenerator
- Properties under
autoGeneration
Property | Description |
---|---|
|
required Parent node for autogenerated content. Anything you define under this node will
be autogenerated. To create multi-value properties, see the |
|
required Name of the autogenerated component. |
|
required When set to |
|
required Component ID in |
|
required, default is
Class that generates nodes based on the definition. The default
info.magnolia.rendering.generator.CopyGenerator creates a
copy of the exact nodes and properties you define under the |
Component autogeneration in SPA
See Component autogeneration and inheritance in the Headless Docs.
For this usage, the endpoint must be configured with $type: jcrPagesDeliveryEndpoint_v2 .
|