Redirects and Deprecations
Redirects and deprecations preserve reader trust when URLs, canonical homes, or page scopes change. A moved page should not silently strand old links, duplicate derivations, or leave readers guessing which version is authoritative.
No public redirect or deprecation entries have been recorded yet for the current draft build.
What Belongs Here
Section titled “What Belongs Here”Record:
- renamed pages,
- moved pages,
- deprecated pages,
- canonical-home changes,
- merged duplicate pages,
- split pages,
- redirect-style replacement notes,
- sidebar reorganizations that affect durable navigation.
Entry Format
Section titled “Entry Format”| Field | Meaning |
|---|---|
| ID | stable maintenance identifier |
| old path | previous path |
| new path | replacement path |
| change type | redirect, deprecation, merge, split, rename, or canonical-home change |
| reason | why the change was made |
| status | planned, active, complete, or superseded |
| date | date changed |
| affected inbound links | pages updated or pending |
Deprecation Requirements
Section titled “Deprecation Requirements”A deprecated page should:
- keep its URL when possible,
- set
status: 'deprecated', - identify the replacement page,
- explain why the page is deprecated,
- avoid preserving stale duplicate derivations,
- keep only the minimum historical or migration context needed.
Canonical-Home Changes
Section titled “Canonical-Home Changes”Canonical-home changes need extra care. Before changing one:
- identify the old canonical page,
- identify the new canonical page,
- update cross-links,
- remove duplicated derivation content,
- record the change here,
- run build checks.