Reorganize argo_translation.yml into components for comprehensive content translation coverage

Rasam Hossainrequested to merge
rasamhossain/new-argo-yml-criteria into main

Summary

This MR restructures the argo_translation.yml configuration file to organize all translatable content in the project into logical components. This ensures comprehensive translation coverage across all content types while maintaining clear separation of concerns.

Reorganized translation configuration into components: Grouped content by type/purpose rather than using a single monolithic configuration. Here's a brief overview of each component:

  1. GitLab Marketing About Site (6 languages) Main marketing content including all pages, base locale files, and shared content. Excludes blogs, events, case studies, topics, and internally-managed pages.
  2. GitLab Blogs (3 languages: ja-jp, fr-fr, de-de) Blog posts only. Manual request creation with custom branch naming for CMS workflow.
  3. GitLab Case Studies (6 languages) Customer success stories and case studies. Manual request creation.
  4. GitLab Topics (6 languages) Topic-specific content pages. Automatic request creation enabled.
  5. Internally Translated (6 languages) Content translated by internal tools including pricing, free trial, release notes, analyst reports, and GitLab Duo pages. Manual request creation only.

Note: All content will be visible in the Argo dashboard including last updated timestamps. This provides full visibility into translation status across all content, regardless of whether translations are managed through Argo workflows or internal tools.

Testing

  1. Verify all content paths in /content/ are matched by component paths
  2. Confirm no unintended files are excluded via ignored_paths
  3. Validate YAML syntax is correct
  4. Check that component names accurately reflect their content type

Related Documentation

Argo Translation YAML Documentation

2. QA Checklist

[This merge request should follow all best practices utilizing our team code standards and our project's development documentation]

  • Code Cleanup: Any messages, linter warnings, and/or deprecation warnings are cleaned up in the console
  • Tech Debt: I have created, or documented, any fast follow-up work that needs to be done after this MR is merged
  • Common Component Regression Check: I have verified all impacted pages of my common component updates have been checked for regressions and UX is aware of any wider-scoped visual changes
  • Efficient Code Review: I have tested and reviewed my own changes thoroughly before assigning a reviewer
  • Accessibility: Axe tools run and issues addressed
  • Cross-browser compatibility: Works on Safari, Chrome, and Firefox
  • Analytics and SEO: Compatible with Google Analytics and SEO tools
  • Localization checked for regressions

[Provide concise steps to test the changes]

Review App

Production Review app Screenshot
https://about.gitlab.com/ N/A Screenshot

3. Deployment Steps

[List key deployment steps or configurations]

Edited by Lauren Barker

Merge request reports