Language Consolidation Overview

There are many (over 70) different locales for the product. Each locale is a combination of language and country. Proposed solution: unify the different languages into one version of each language, creating a more sustainable approach to country expansion and the management of content/translations.

Build a process that enables the team to manage unique country values through fallback keys instead of locale. Utilize country files on the front-end (FE) of the product to implement Customer Service phone numbers, legal documents URLs, etc, as documented in the tickets.

1. Create and document the base versions of each language
2. Tag any keys that contain country-specific content
3. Build new keys, using the new naming convention: key.name.label_countrycode
4. Use tokens to implement dynamic values coming from the country files: eg. {{contactPhone}}
5. Work with developers to implement solutions for the back-end (BE) fields

Create a product that no longer relies on country-specific locales to manage unique content. All versions of English should utilize the locales: en-us and en-gb

Create a product that has all languages available to the users. Eg. People in Poland can still use French.

Implementing language consolidation will allow the content managers to focus on the quality and storytelling in the various products by decreasing the content managed by nearly 60% across the various platforms. 

Revenue implications: Customers will now be able to use the products in over 20 unique languages. Potentionally increasing trust and the usability of the product.

Creating a unique value prop compared to competitors. No other money transfer company opporates in this way.