Configure Hugo aliases for all moved content for SHIP-0041

[adambkaplan]

Overview

This task ensures all moved documentation has Hugo aliases configured to automatically redirect from old URLs to new locations as described in SHIP-0041.

Description

Ensure all moved documentation has Hugo aliases configured to automatically redirect from old URLs to new locations. Test redirects work correctly in both local preview and production deployment.

Hugo aliases are configured in the front matter of each page:

aliases:
  - /old/path/to/document
  - /another/old/path

Acceptance Criteria

• Hugo aliases configured for all moved content
• All old paths from migration plan have corresponding aliases
• Redirects tested and working in local Hugo preview
• Redirects validated in production deployment
• No broken external links
• Redirect chain validation (no redirect loops)

Dependencies

• Blocks: Validate and fix all internal documentation links (Issue 11)
• Blocked by:
  • Migrate existing content to Concepts section (Issue 4)
  • Migrate existing content to How To section (Issue 5)
  • Migrate and enhance Reference section (Issue 6)
  • Migrate in-tree documentation from build repository (Issue 7)
  • Migrate in-tree documentation from cli repository (Issue 8)
  • Migrate in-tree documentation from operator repository (Issue 9)

Technical Notes

• Use the migration plan to identify all old paths that need aliases
• Configure aliases in the front matter of each migrated document
• Test redirects locally using hugo server
• Verify redirects work in production (Netlify deployment)
• Check for redirect chains and optimize if needed
• Consider creating a script to automate alias configuration if there are many documents

---

Generated-by: Cursor