Site changes / context web / MD84
Resource move workspace
Inspect the branch. Resolve path collisions. Retain the approved URL map.
Site resources6 records
Selected branch2 resources
Site revision4
Single context · web
A parent move includes its child
The selected Specs branch is resource 21 and child Install 22.
| ID / resource | Parent | Current path |
|---|
Support already contains Specs 31
Moving 21 under Support 30 with alias specs would collide at /support/specs.
Receiving checks
- Branch scopeKeep resource 21 and child 22 together
- Destination pathsCheck all six existing resource identities
- Tree integrityRefuse a descendant as the new parent
- Release handoverRetain both old-to-new redirect rules
Example URL policy
One context, slash-separated aliases and no content-type suffix. Preview uses the current revision. Publisher confirms a valid move.
Move request / resource 21
Choose a parent and a distinct alias
Specs 21 carries Install 22 with it.
Preview the destination paths before approval.
| ID | Old path | New path |
|---|---|---|
| No current preview. | ||
Resolve the collision
With parent 30 and alias specs, resource 31 already owns the destination path.
Use alias technical
21 → /support/technical
22 → /support/technical/install
Editing the parent or alias clears the prepared approval. An external edit advances the site revision.
Revision check / release approval
Accept the complete URL map
No valid move prepared.
| Old path | Destination path | Code |
|---|---|---|
| Preview a valid move first. | ||
Retained move receipt
No move accepted.
The receipt keeps the accepted IDs, original paths, destination paths, role and revision. It survives later input edits.