Where the path comes from
| Option | Meaning |
|---|---|
Parents |
The relations from a node to its parent, in priority order. Empty means flat. |
Domains |
UrlDomain { Host, RootId }: each host serves the tree below its root node, and the root is /. |
FallbackRootId |
The root for unknown hosts: localhost, staging, tests. Default: the first domain's root. |
OwnHosts |
More hosts the site runs at, separated by commas: "staging.site.com, localhost" (§18.2). |
Scheme |
Scheme of absolute URLs. Default https. |
MaxDepth |
Limit on the walk up the parents, against cycles. Default 32. |
A UrlParentRelation names its relation by ParentRelationName (CodeName or full name) or
ParentRelationId; ParentIsRelationSource (default true) puts the parent on the source side. With
several Parents, the manager follows the first that accepts the node's type and has a parent for it.
So pages can hang under pages through one relation and documents under pages through another, and one
URL crosses both. Domains are not stored on nodes, so the same content runs unchanged on localhost.
Shop (root) → /
├─ tv → /tv
│ └─ sony-x90 → /tv/sony-x90
│ └─ info → /tv/sony-x90/info
└─ mobile
└─ pixel
└─ info → /mobile/pixel/infoBoth leaves have the address info. An address only has to be unique among nodes that would
otherwise get the same URL.