**Project Objective** Localization and Technical Writing are partnering to localize documentation site for tier one markets aligned with GitLab business needs (Japanese, German, and French). In order to continue to compete in these markets and align with industry standards, since our product is localized, we also need documentation that is localized. Our tier one languages are our largest markets that are also the least tolerant of having language experiences outside of their native language. Research has shown that prospective customers are more likely to make a purchase when they are able to do so in their native language. Additionally, more and more of our business is coming from geographies outside of AMER over time. Finally, GitHub docs are localized in 8 languages outside of English, and they started their support localization journey in Aug 2022. For the reasons above, it is critical that we localize our key assets, to support our global expansion and continued company growth. GitLab has aligned on localizing tier one languages, starting with Japanese, post-Hugo integration in FY26. **Project Goals** - Align on roles and responsibilities across localization, technical writing, and vendor teams - Understand TW workflows and collaborate with vendor management team on how to integrate Argo - Understand concepts, capacity, and resources needed to support localization - Understand, determine, and resolve impending roadblocks or concerns for localization on documentation site - Launch localized Japanese in FY26 (with documentation set up as part of translation ecosystem ) Handbook page: https://handbook.gitlab.com/handbook/marketing/localization/tech_docs_localization/