How we built and automated our new Japanese GitLab Docs site

What this post added

This post details the technical implementation of the Japanese GitLab Docs site. Key contributions include: 1. Integrating new `doc-locale/ja-jp` folders within existing English content structure for co-location of translations. 2. Developing custom code and regex in the Translation Management System (TMS) to protect code blocks, URLs, and other functional markdown elements from translation. 3. Establishing an English fallback mechanism using Hugo's rendering system to display English content with translated navigation when Japanese translations are incomplete. 4. Extending CI/CD pipelines to test localized content in Translation MRs, catching invalid Hugo shortcodes, spaces in links, bare URLs, orphaned files, and redirects. 5. Implementing dynamic anchor ID generation by pre-processing English files to ensure consistent linking across languages. 6. Orchestrating a centralized translation request system to monitor English files, route for translation, create translation MRs, and track file status.