[Discussion and plan] Anchor links validation in translated content for launch and later on

Background

Related to https://gitlab.com/gitlab-com/localization/tech-docs-forked-projects/prod/gitlab/-/merge_requests/688. Attempt to clarify how we will handle the anchor link validation failure in translated content for launch (December) and over time (continuous localization in place).

Problem Statement

As we prepare for launch, some anchor link failure in translated content is expected as LOC is not in continuous sync with the source yet. We are unable to establish a fallback to English because the content the broken anchor points to is translated, it's just missing an English anchor, so there is no fallback solution for anchor links.

Proposed Solution

Flexibility in the technical approach with regard to pipeline pass, i.e. have the pipeline produce a warning as opposed to fail on failed anchor links.

Potential Impact

Temporary UX impact at launch and shortly after that should lessen and cease as we establish the continuous localization workflow.

@laurenbarker @jcole-ext @opysaryuk @mjsibanez

Edited by Iryna Rogova