<page folders> | Pages (mgnl:page) are stored in folders: - The page folder-structure matches the website tree structure.
- There are content nodes for each page area .
- All area nodes reside at the same level, regardless of whether configured as main or nested Area definition#Creatingnestedareas areas.
|
<area nodes>
| Areas (mgnl:area) are stored in content nodes:
single and list areas have component subnodes.noComponent areas can be used in various ways but typically have only area properties.
|
<component nodes>
| Components (mgnl:component) are stored in numbered content nodes: - Node numbers are sequential and assigned automatically.
- Nodes display in the same order as on the page.
- Assigned number depends on when the component was created. Rendering order may not match numbering order.
- Components with nested components follow the same structure as area nodes. This coincides with the component definition configuration.
|
<component properties>
| Component properties are stored under the component node: - Property names correspond to dialog field names.
- By default i18n properties have a locale suffix.
|
<area properties>
| Area properties, if any, reside under the area node. |
<page properties>
| Page properties reside under the page node: - Property names typically correspond to field names in the page properties dialog.
- Components or areas can also add page-level properties.
|
