[PAGES-357] DOC: Best practice for moving pages after publication Created: 08/Oct/20  Updated: 04/Feb/22  Resolved: 04/Feb/22

Status: Closed
Project: Magnolia pages module
Component/s: None
Affects Version/s: 6.2
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Richard Gange Assignee: Richard Gange
Resolution: Won't Do Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MAGNOLIA-8053 Copying JCR items should strip activa... Closed
is related to MTE-115 MTK should provide a redirect page te... Closed
is related to PAGES-358 DOC: Best practice for renaming pages... Closed
is related to MTE-126 Best practice actions for public faci... Closed
is related to MGNLSYNC-51 Synchronisation may fail when nodes a... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Documentation update required:
Yes

 Description   

A page node can have many different states. Versioned/Not versioned. Published/Not published. Modified/Current.

After a page has been published we should consider disabling the move operation. Best practice from an SEO perspective is to redirect to the new location. Therefore, a published page cannot simply be moved. It needs to be "deprecated" with a redirect template to its new location. The new node should be a copy of the old node and disconnected from the the version history. In simple terms, moving to a new location is like stating a new life.

We could consider creating a "mgnl:copiedFrom" metadata which contains the uuid of the original node.


Generated at Mon Feb 12 06:18:09 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.