WIP Translation process improvements

[pdcp1]

Pain points

1. Env variable

GATSBY_AVAILABLE_LANGUAGES=en,es,fr,ja

2. i18n config file

site/gatsby-site/i18n/config.json

3. UI translations

JSON files with the translations under the folder site/gatsby-site/i18n/locales/[language code]. E.g: site/gatsby-site/i18n/locales/ja/account.json

Improvements

• The meta i18n page helps to identify pending translations
• We should implement fallback to English translations when a new text lacks a translation.

4. Site language switcher

Change site/gatsby-site/src/components/i18n/LanguageSwitcher.js code adding the new language

5. Atlas rules

Add the Atlas rules file for the translations/reports_[language code] collection.

Improvements

• We are going to leave Atlas soon ✅

6. Gatsby type definition

Add Gatsby type definition to this file: site/gatsby-site/typeDefs.js

7. Sorting option on Discover page

Add Sorting option to Discover page for each field: site/gatsby-site/src/components/discover/SORTING_LISTS.js

Improvements

• We should add these fields programmatically (e.g.: value_ja: 'instant_search-ja_epoch_incident_date_asc') iterating on the GATSBY_AVAILABLE_LANGUAGES language list
  • Refactor Discover sorting options to use a dynamic language list #3271

8. Report translation MongoDB query

Add report translation query on site/gatsby-site/src/graphql/reports.js

Improvements

• Change the way we store the translations. Using just one reports collection with a new document field language.
• Change the API to use this new DB approach
• Change the client graphql mutations

9. Blog posts translations

Not mandatory since we have translations fallback to English