Localization of GitLab Product Documentation – Post-launch Feedback

Overview

This issue gathers feedback on the new docs.gitlab.com/ja-jp site. The site delivers localized GitLab product documentation, enabling Japanese users to learn about GitLab features and find answers more quickly in their own language

How to give feedback

We welcome any type of feedback. Whether you're curious about how AI-assisted translations work, why some pages still show English content, or the internationalization details behind the site, everything is documented in our new Handbook page: https://handbook.gitlab.com/handbook/marketing/localization/tech_docs_localization/

We'll appreciate it if you can:

• Check existing feedback & known issues: Before submitting, check to see if your feedback is already captured or reported by someone else in this issue or explained on the Handbook page. If so, comment on the existing thread or leave an emoji reaction to show support.
• Start a new thread: If your feedback is not listed, start a new thread with a descriptive title. Include relevant details, screenshots, and steps to reproduce the issue in expandable sections.
• Be specific: Provide as much detail as possible, including device/browser information, steps to reproduce, and expected vs. actual outcomes.

## Bug Report Template

#### [Bug Title]
1. **Bug**: [Clear description of what's broken]
2. **Where**: [URL(s) or location where bug occurs]
3. **Reproduce**: [Step-by-step instructions to recreate the issue]
4. **Browser/device**: [Link to https://whatismybrowser.com]
5. **Expected vs Actual**: [What should happen vs what actually happens]
6. **Severity**: [Critical/High/Medium/Low]
7. **Screenshot**: Visual evidence (if applicable)

What you can expect from us

1. We will read all of your feedback.
2. We will respond to all feedback directly.
3. We will create issues for repeatable bugs and assign a priority based on severity.

Feedback Threads Tracker

• ...
• ...

Known issues

Some details are covered in the "Known limitations and future work" section of our Handbook page.

Note

Our translation coverage of the site is not completed yet so it's expected to see pages showing up as untranslated.

1. Search bar in the docs site search only works in English.
2. The JA page may not be at 100% sync with all the content that appears in English. There's a disclaimer banner at the top that informs users about this discrepancy and that some translations are AI-assisted.
3. Homepage links: some links on the JA homepage (docs.gitlab.com/ja-jp) will link out to an English page:
   • Link to https://university.gitlab.com/learn/dashboard -only available in English
   • Link to https://about.gitlab.com/support/ -only available in English
   • Link to https://about.gitlab.com/community/contribute/ -only available in English
4. All the links in docs.gitlab.com that redirect the user to about.gitlab.com will remain in EN. For example, footer links in the homepage.
5. 404 error message is only available in English. See reasoning here.
6. We've implemented an fallback mechanism where a non-EN user would see first content in EN than a 404 error message.
7. The content in the "contribute" menu remains in English in the localized site. Read through rationale here. The JA page contains a disclaimer that takes you to the main English "Contribute to development" page. A JA user can use the language selector in the top nav to go to the corresponding English "Contribute" page that they're currently seeing.
8. GitLab Terms of Use are only available in English intentionally and agreed upon with GitLab's Legal Team
9. GitLab's social media links link out to EN accounts.
10. Footer links:
    1. "View page source" and Edit in Web IDE redirect to English files.
    2. The "Cookie Settings" link opens up the English GitLab's Privacy Preference Center powered by Onetrust. The translations of that modal are supplied by Onetrust.

Thank you!