CONTENT ENGINEERING / PAGE TREEScope: Support subtree · revision 7

Move a section. Keep every route accountable.

Rehearse a three-page relocation before agreeing the development and migration scope.

3Pages in the selected subtree

0Accepted route changes

0Redirect entries retained

Selected source: Support

P210 · Support
/support

Selected root

P211 · Returns
/support/returns

Child

P212 · FAQ
/support/faq

Child

Content revisions: P210 r12 · P211 r8 · P212 r5. The exercise changes routing only.

Destination inventory

P400 · Company
/company

Available parent

P450 · Staff support
/company/support

Existing route

P500 · Knowledge base
/knowledge

Available parent

The Company section already contains “support”. Give the relocated root a distinct URL segment before accepting its new paths.

Define the move

New parentRoot URL segmentActing role

A tree edit advances the source revision. Preview the current routing again before acceptance.

Inspect old and new destinations

Build a preview to test destination conflicts and descendant paths.

Page	Current path	Proposed path

I have checked all three destinations and the old-path redirect map.

No routing change accepted. Current public paths remain in the source section.

Redirect handoff

Accept a valid plan to produce the three-entry redirect receipt.

Receipt: TM31-R1
Change scope: Routing only · three stable page identities
Source snapshot
Acceptance role: Migration owner
Content versions: P210 r12 · P211 r8 · P212 r5 · preserved

Page ID	Old route	New destination	Handoff rule

Acceptance scope: configure and test one-hop permanent redirects in the agreed deployment. Confirm actual responses, final content and caches in staging.

No receipt issued yet.