[PAGES-358] DOC: Best practice for renaming pages after publication Created: 08/Oct/20 Updated: 22/Feb/23 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: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| 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 rename operation. Best practice from an SEO perspective is to redirect to the new location. Therefore, a published page cannot simply be renamed. 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, renaming a node is the same thing as creating a new node. The steps should be:
Notes |
| Comments |
| Comment by Richard Gange [ 19/Oct/20 ] |
I think the hasVersion rule would work here. This is core of this problem. When you rename the node it has side effects for publication and synchronization. Not to mention it's bad for SEO. For example, if I rename a page in confluence it will suggest to me the page was moved. Our system doesn't do that. In the release notes we should mention the change because that action has been around a long time. To simply disable in this state might be confusing to users. We need to mention the SEO best practices for renaming pages. I think it also could use a mention in the pages app docs as well. |