Imported indicators and geographies have a single language name.
If we want to support i18n later, we can add a model for translations, and make it available in the Django admin.
Another option is to do translation in the source files (e.g. indicatorTitle_es, etc. columns), but I don't think that matches the flow of the project.
Or, we can have entirely separate deployments for each language backend. This is simplest to develop (just change the backend API base URL when switching languages), but probably the most work to operate (sync geometries, etc.).
Imported indicators and geographies have a single language name.
If we want to support i18n later, we can add a model for translations, and make it available in the Django admin.
Another option is to do translation in the source files (e.g. indicatorTitle_es, etc. columns), but I don't think that matches the flow of the project.
Or, we can have entirely separate deployments for each language backend. This is simplest to develop (just change the backend API base URL when switching languages), but probably the most work to operate (sync geometries, etc.).