@Siumauricio Do you mind if I add i18n support first?
Translation replacements for zh-Hans will be done incrementally later, I'm doing this because given the fast pace of the project's development, a full translation might take too long and make merging difficult.

@Siumauricio Also, do you have any particular preference for the i18n solution?
I use the https://github.com/i18next/next-i18next.

@Siumauricio Maybe we can use some tools like https://github.com/WeblateOrg/weblate to handle translations manager 🤔

Sounds good to incrementally add translations, how much weight will this add to the final docker image?

btw I removed the internationalization in the docs because it was honestly very difficult to keep translations up to date and it was better to stay in English for the time being

Sounds good to incrementally add translations, how much weight will this add to the final docker image?

btw I removed the internationalization in the docs because it was honestly very difficult to keep translations up to date and it was better to stay in English for the time being

I don't think it will add too much, these are simply JSON files, that said, is there any way we can test it?

Ill add german once this is merged!

Ill add german once this is merged!

haha😉. For those contributors who start translating in the first place, they have to complete a basic English Key extraction.
Then later contributors who add another language can just copy locale.json