[10k]: Translation process & contracts

[widal001]

Description

Implement a process (preferably an automated one) that makes translations quickly and accurately available for content.

This could include using the State Department for translation like many USDS websites do, or setting up external bounties for translation such as those used by Open Collective Foundation: https://docs.opencollective.com/help/contributing/translation#bounties.

Preference for integrating the external team that does translations directly into the codebase so they can make their own pull requests to content.

Define languages planned on support for website. The most common languages are published by the Census: https://www.census.gov/library/stories/2022/12/languages-we-speak-in-united-states.html. A reasonable option for a starting point for supported languages would be Spanish and either Mandarin or Cantonese (the Census marks both of these as 'Chinese' so it is not clear which is the 3rd most commonly spoken language in the US).

For language data, there is more detailed microdata found in the Microdata Access Tool (MDAT). Here's a table using the 2021 1-year ACS Public Use Microdata Sample (PUMS) file: https://data.census.gov/mdat/#/search?ds=ACSPUMS1Y2021&rv=HHLANP&wt=WGTP.

Ideally, every release of new content should be followed shortly thereafter by translations in key supported languages. Milestones will not be complete until their related content is released in all supported languages.

Dependencies

• [x] #49
• [ ] #75
• [x] #76
• [x] #64

Sub-Tasks

TODO

Definition of Done

TODO

[widal001]

Replacing our old 10k ft deliverable issues with a new Epic format

[widal001]

Reopening for review during sprint planning