Samuel Silva

You could just create a page example showing up how to use it, it'd enrich the project since the goal is to create a "Flexible production-grade boilerplate" right?

Ideally in all pages, including a specific example page would be great to illustrate and add more documentation about its usage.

@Vadorequest 20 languages, this started happening recently, it was not happening before.

Ok the problem is because I changed how locize fetch languages from: ```typescript const i18nTranslations: I18nextResources = await fetchTranslations(lang); // ie: fr ``` to: ```typescript const i18nTranslations: I18nextResources = await...

I already have `es-CO` and `es-ES` on locize, I don't have `en-CO` because this isn't even a valid locale. It's not about design, it's about the languages I need to...

> Then the error message seems to point out those languages don't have a `common` namespace on Locize. Which is weird because they're already have the `common` namespace:

> It's not about Locize, but about how i18next works What do you mean? As far as I know i18next support variation as any other language.

I can see that the translations are being fetched and returned properly from Locize, so in fact it's not a problem with Locize.

I think the problem is a misconfig using `lang` rather than `locale`, but I didn't find it, if you could try to reproduce it including a language variation to see...

Any feedback here @Vadorequest ?