fix: add redirects for legacy /{lang}/flashduty/* paths (335 URLs) - #252
Merged
Conversation
The docs site restructure moved all pages out of the old flat
/{lang}/flashduty/<slug> structure into sectioned paths (on-call/,
compliance/, monitors/, rum/, ...), leaving every legacy URL to 404.
Add 335 redirects mapping each legacy path still referenced by product
UIs, emails and published content to its new location; every
destination was verified live (HTTP 200) before inclusion.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The docs site restructure moved all pages out of the old flat
/{lang}/flashduty/<slug>structure into sectioned paths (/on-call/...,/compliance/...,/monitors/...,/rum/...). No redirects were configured, so every legacy URL — still referenced by product UIs, transactional emails, and published content — returns 404. Example:/zh/flashduty/user-aggrement(linked from the subscription purchase page) → 404.Change
Adds 335 entries to
redirectsindocs.json, mapping each legacy path that is still referenced anywhere to its new location:user-aggrement/privacy-policy/data-security/service-level-aggrement→/compliance/**-integration-guide→/on-call/integration/{alert-integration/alert-sources,instant-messaging,sso,webhooks}/<name>(incl. renamed slugs such asnightingale→flashcat,feishu-alert→lark-alert,gcpcm→google-cloud-monitoring, and legacy misspellingsharboe→harbor,skywallking→skywalking)/on-call/...,/platform/...,/monitors/...,/rum/...equivalents/{lang}/flashduty/root →/{lang}/on-callVerification
https://docs.flashduty.comand returns 200 (326 destinations verified individually during mapping; all 335 sources have a verified destination).jq empty docs.jsonpasses.