Closes #4. To implement internationalization using nuxt's own i18n library.
What I changed
Installed @nuxtjs/i18n and configured it as a module in Nuxt config. We are detecting the browser language and setting the strategy to no_prefix.
Added English, Spanish, Dutch, and Portuguese translations.
Implemented translations wherever any strings are found in the app.
What I'm not doing here
Adding a language switcher dropdown, as done for MapPacker. Mainly because the GCV landing page (index.vue) is not fully exposed to the user as of yet (instead, we are embedding specific views). So we can cross that bridge when we get there.
As mentioned above, setting a prefix strategy. We can revisit that if we see the need for one of the Nuxt apps.
Goal
Closes #4. To implement internationalization using nuxt's own i18n library.
What I changed
@nuxtjs/i18nand configured it as a module in Nuxt config. We are detecting the browser language and setting the strategy tono_prefix.What I'm not doing here
index.vue) is not fully exposed to the user as of yet (instead, we are embedding specific views). So we can cross that bridge when we get there.