Problem Statement
Docs team currently planning a comprehensive restructuring of our documentation portal’s Information Architecture (IA).
However, we face a systemic challenge that complicates this initiative: a high volume of hardcoded, absolute documentation URLs have been embedded across external marketing collaterals and internal source code repository READMEs.
Modifying our content hierarchy without a mitigation strategy will break these critical touchpoints, resulting in a fractured user experience and a high volume of broken links. I would like to learn how industry-leading teams systematically resolve this issue, and establish a framework for our organization to decouple source documentation from public-facing URLs moving forward.
Problem Statement
Docs team currently planning a comprehensive restructuring of our documentation portal’s Information Architecture (IA).
However, we face a systemic challenge that complicates this initiative: a high volume of hardcoded, absolute documentation URLs have been embedded across external marketing collaterals and internal source code repository READMEs.
Modifying our content hierarchy without a mitigation strategy will break these critical touchpoints, resulting in a fractured user experience and a high volume of broken links. I would like to learn how industry-leading teams systematically resolve this issue, and establish a framework for our organization to decouple source documentation from public-facing URLs moving forward.