**Goal** Create optimal configuration for the argo_translation.yml file to enable continuous localization of GitLab product documentation, configure and add the file to localization forks and upstream projects. \*\*\*\*\*\*\* # Summary How the will the argo_translation.yml will need to be configured to enable continuous localization? This issue will investigate a best path forward along with documenting these steps. The team will need to determine: * Role of argo_translation.yml on the forks * Role of argo_translation.yml on the upstream projects * What is GITTECH translation request type (to document after launch; not critical) * How do we config argo_translation.yml file in case we want to go with AI-only translated files on production by launch? The localization team is would like to add argo translation yaml to configuration files for upstream projects. This would need to reviewed by Legal and TW team. @opysaryuk to add additional details. # Pre-requisite _Add any steps to be performed before end to end testing can begin_ * [ ] Set a milestone / timeframe for the test session issue to inform all the DRIs about the upcoming testing session. * [ ] Dev leaders identify a DRI to participate in the testing session. * [ ] Ensure all testers have the right access/permissions in all our applications (i.e. GitLab, docs, etc.) for testing purposes. * [ ] All DRIs have reviewed issue in full and read applicable information below * [ ] Ensure all system DRIs have reviewed the new test scenarios and approved the changes. > * [ ] Technical Writing Staff Engineer: `@handle` > * [ ] Localization Engineer (Senior+): `@handle` > * [ ] Technical Writing (Manager +): `@handle` > * [ ] Localization (Manager+): `@handle` > * [ ] Spartan Vendor: `@handle` * [ ] Communicate an estimated time for testing completion for DRIs # Potential Test Cases | Scenario # | Task | Test Case | Scenario | Expected Outcome | UX sign-off | |------------|------|-----------|----------|------------------|-------------| | | | | | | | ## What to look out for - Sagittis facilisi - Example: Congue justo erat malesuada fermentum, tristique luctus metus. Torquent venenatis montes sollicitudin lacinia cursus interdum. Augue feugiat aliquam vitae parturient nibh, urna metus. - Lorem ipsum odor - Example: Vel inceptos ad lacinia nibh habitasse lobortis eros lectus. - Montes sed potenti - Example: Venenatis nisi arcu proin risus ridiculus tempus ornare ## Known issues / bugs - [Known bug list](gitlab.com) mattis condimentum odio curae euismod felis mus eros. - Gravida dui mus dictumst - Mattis condimentum odio curae euismod felis mus eros. Magna aliquet ut lacinia in facilisi litora. Congue facilisis lacus nisi est eu maximus. Turpis rutrum velit penatibus est luctus sapien morbi. - Current UI for language selection will be updated in Q1 (see gitlab.com) - Tellus imperdiet hac interdum primis dolor tellus aptent dictum. Habitasse nostra phasellus scelerisque fusce dapibus rhoncus vel curabitur. :bug: Please use the [Bug template](https://gitlab.com/gitlab-org/technical-writing-group/gitlab-docs-hugo/-/issues/new?issuable_template=Bug) for reporting bugs. ## User-facing features that not yet implemented - gitlab.com - Version-specific behavior (gitlab.com) - Tellus imperdiet hac interdum primis dolor tellus aptent dictum. Habitasse nostra phasellus scelerisque fusce dapibus rhoncus vel curabitur. - Sed ut ipsum pellentesque dictum congue accumsan maecenas dictumst (see: gitlab.com) ## Out of scope for this project - Significant visual design changes - Translations ## Next steps in the project We'll continue working through \[this epic\] (gitlab.com) - Next step #1: [link here](url) - Next step #2: [link here](url) - Next step #3: [link here](url) - Next step #4: [link here](url) - Next step #5: [link here](url) ## How to provide feedback Before you start, please be sure to follow applicable action steps listed above and only provide one piece of feedback per thread. Below are the action steps to follow: * Check the known issues. * Review + check potential use test cases for clarity and accuracy * Review comments and/or feedback threads on this issue * If the feedback is not already covered in a known issue or feedback thread, open a new child issue on this issue. The DRI will respond and close the thread by either answering the question or opening a new backlog issue or bug in the project. * Open child item for any concern areas or areas that need additional support ## Sign-offs _Once all scenarios have passed validation, stakeholders will provide final sign-off below_ * [ ] Technical Writing Staff Engineer: `@handle` * [ ] Localization Engineer (Senior+): `@handle` * [ ] Technical Writing (Manager +): `@handle` * [ ] Localization (Manager+): `@handle` * [ ] Spartan Vendor: `@handle` * [ ] Legal Counterpart: '@handle'