Localisation
2 minute read
Background
intelliHR is an open and inclusive company committed to ensuring that every customer has equal access to the platform
Part of this means ensuring that the platform is localised and translated so that users who do not speak English natively are still able to navigate and use the platform.
intelliHR has selected Lokalise as its translation platform as it’s simple, easy-to-use, and extremely powerful. It offers automated DeepL translation, contracted translation services, and bulk language creation for minimal cost.
If you’d like to read more about Lokalise, check out this link.
intelliHR’s Localisation Repository
You can find the repository that intelliHR uses for storing its source strings here. Where strings do not need to be stored in a database, they should be stored in this repository, as it is the source of truth for the source strings.
Each engineering team has its own set of <team>.yml files that keys are stored in. These are common formatted YAML files with linting.
Database Localisation
In many cases, it is not practical to store a string inside a .yml file. In this instance, your table should have a i18n_key column, with a reference to the key_name that you use in your feature’s code. Read more about database localisation.
Local Environment
When developing locally, you will have a copy of all the .yml files used for the base en language in both lapis and spa. This will enable you to rapidly iterate and develop new features, but will mean that you only have access to en in your local environment. Local development with localisation was identified as a big pain point by developers, necessitating this behaviour, and you can read more about it here.
Localisation Best Practices
In order to ensure intelliHR can provide best-in-class localisation services, developers must ensure that they adhere to best practices. Whilst not exhaustive, a guide has been developed, should you any questions about localisation. If you still have questions after reading the best practice guide, please ask Team SOSO for help, as they are the owners of intelliHR’s localisation platform.