feat(frontend): Add i18n to the website

[esau-morais]

Expected

More languages (English, Spanish, at least)

Actual

Just portuguese

What is i18n?

Internationalization (i18n) is the process of preparing software so that it can support local languages and cultural settings. ... I18n is product development focused so that in the case of software, one code base is made capable of supporting worldwide languages and locale-specific formatting and behaviors

Why you should add i18n feature

Open-source supporting → I think this is enough to explain how important it is.

Steps

• [ ] Install react-i18next library
• [ ] Make the translations
  • [ ] English (United States)
  • [ ] Portuguese (Brazil)

[ramos-ph]

Thanks for your suggestion, Esau!

Could you solve this issue with a Pull Request? Do you have time and knows how to begin with?

[esau-morais]

Thanks for your suggestion, Esau!

Could you solve this issue with a Pull Request? Do you have time and knows how to begin with?

Yes, how I explained in the community, the issue is just a validation to the pull request. I need the community participation to continue.

Regards, Esaú

[ramos-ph]

Feel free to contribute! I will open a Project board here.

The data is also stored in Brazilian Portuguese. Do you have any idea of how workaround this without flooding the database?

[esau-morais]

Thank you!

Yes, I just need to analyse the project before

[stevescruz]

I agree with this issue, I planned to talk about this in the meeting saturday. I am interested in learning how to implement this. I can also translate PT-BR to English and Spanish.

[esau-morais]

I agree this issue, I planned to talk about this in the meeting saturday. I am interested in learning to implement this. I can also translate PT-BR to English and Spanish.

Good to know. The translations are the hardest part, we need to review well too

[ramos-ph]

We have an API Reference available in the other repo that's filled with request and response examples.

I highly recommend that you give a look. That way we can discuss what is the best way to do it.

Follow the link: https://github.com/Lorenalgm/DevChallengeAPI/blob/master/REFERENCE.md

[stevescruz]

By the way another thing we should decide upon is to define a more strict language policy for commits and issues to standardize it. But this is off-topic.

[ramos-ph]

@stevescruz Please see: https://github.com/Lorenalgm/DevChallengeAPI/tree/master/.github

[esau-morais]

We can continue this discussion in the community.