Remove product translation specs and migrate glossary to marketing

Decision (2026-01-13)

Based on localization engineering iteration planning meeting discussion, and summary thereof here: #13 (comment 3003774138)

Remove product specifications entirely because:

• GDATP is used for marketing content (about.gitlab.com)
• Product UI labels are translated using Crowdin (epic GitLab Product Localization (&24))
• Product docs are translated using separate tooling (tech-docs-ai-powered-translation)
• Product specs create conflicting guidance (e.g., opposite nominalization advice - see details here: #13 (comment 3003782141))

Action plan:

1. Migrate specifications/product/languages/ja-jp/glossary.csv to marketing
   • Rename to termbase.csv (required by GDATP system prompt)
   • Replace existing specifications/marketing/languages/ja-jp/termbase.csv
   • Preserves @emikimura-ext's comprehensive terminology work
2. Update GDATP system prompt (remove Product Translation Module) main/system-prompt.md
3. Delete specifications/product/ folder entirely

See detailed analysis in this comment thread: #13 (comment 3003774138)

---

Original Proposal

[Keep existing Problem/Proposal/Benefits sections for context]

Problem

Currently, we have separate translation specifications for product and marketing content, which may lead to inconsistencies in terminology and translation approaches. The product specifications include a comprehensive glossary (e.g., specifications/product/languages/ja-jp/glossary.csv) that could benefit marketing translations.

Proposal

We should consider one of the following approaches:

Option 1: Combine specifications

• Merge product and marketing translation specifications into a unified framework
• Create shared glossaries and style guides
• Establish consistent terminology across all content types

Option 2: Migrate glossary to marketing

• Copy the existing product glossary from specifications/product/languages/ja-jp/glossary.csv to marketing specifications
• Adapt the glossary for marketing-specific terminology
• Maintain synchronization between product and marketing glossaries

Benefits

• Consistency: Unified terminology across product and marketing content
• Efficiency: Reduced duplication of translation work
• Quality: Shared knowledge and best practices
• Maintenance: Single source of truth for translation guidelines

Next Steps

1. Review current product glossary at specifications/product/languages/ja-jp/glossary.csv
2. Assess marketing translation needs and existing terminology
3. Decide on the best approach (combine vs. migrate)
4. Implement the chosen solution
5. Update documentation and processes

Related Files

• Product glossary: specifications/product/languages/ja-jp/glossary.csv
• Product specifications: specifications/product/languages/ja-jp/
• Marketing specifications: (to be identified)