Summary

Several legacy reactonrails.com/docs/guides/* URLs still return 404 instead of redirecting to the current docs structure.

Verified examples

• https://reactonrails.com/docs/guides/file-system-based-automated-bundle-generation.md -> 404
  • modern equivalent: https://reactonrails.com/docs/core-concepts/auto-bundling-file-system-based-automated-bundle-generation/ -> 200
• https://reactonrails.com/docs/guides/configuration/ -> 404
  • modern equivalent: https://reactonrails.com/docs/configuration/ -> 200
• https://reactonrails.com/docs/guides/upgrading-react-on-rails -> 404
  • modern equivalent: https://reactonrails.com/docs/upgrading/upgrading-react-on-rails/ -> 200

Why this matters

• Older help links and external backlinks still break
• Search results can land users on dead routes instead of the current docs tree
• The docs migration is harder to treat as complete while these common legacy paths still fail

Acceptance criteria

• Add redirects for the legacy /docs/guides/* routes that map cleanly to current docs pages
• Verify the examples above return 301/302 to the expected modern routes instead of 404