Implement i18n - Githubissues

Vagabonds-Labs / cofiblocks

Welcome to Cofiblocks marketplace: A Starknet web3 platform to innovate Costa Rica coffee industry. Cofiblocks connects small coffee farmers directly with coffee lovers, cutting out unnecessary intermediaries.

https://www.cofiblocks.com/

12 stars 26 forks source link

Implement i18n #4

Closed brolag closed 1 week ago

brolag commented 2 months ago

Add internationalization (i18n) support using next-i18next to enable multilingual support for the platform.

Steps:
1. Install and set up next-i18next library.
2. Create language files for English and Spanish.
3. Implement language switching in the UI.
Acceptance Criteria: Users can switch between English and Spanish via a language toggle, with all platform content translated.
Resources: Next.js i18n Documentation

muguika commented 2 months ago

We are missing a language switching in the UI that is accesible. At the moment we only have it under Profile > Settings > Language too many steps to get to it, will discuss this with the design team

MaiCVCR commented 2 months ago

Hi,

I'm a software developer with several years of experience, currently involved in web3 projects. I'm from Costa Rica and would love to contribute to this project.

Here's a brief overview of how I would approach this issue:

Set up next-i18next: Install and configure it, creating language files for English and Spanish.
UI Language Switcher: Move the language switcher to a more accessible location. I’m happy to await your input on the preferred placement of the language switcher within the UI.
Translate Content: Implement full content translation and ensure smooth switching between languages.
Testing: Test the functionality to ensure proper language switching and content translation.

brolag commented 2 months ago

@MaiCVCR assining this to you.

MaiCVCR commented 1 month ago

I just submitted a PR with the initial i18n configuration.

I also have a few questions regarding the setup you'd like:

All translations are stored in JSON files. Do you prefer a single file for the entire application or one file per page (e.g., marketplace.json, home.json)?

locales

For storing the selected language, we have a few options: we can use cookies, localStorage, or include the language in the URL (e.g., /es/marketplace). Which option do you prefer?

brolag commented 1 month ago

@MaiCVCR

Thanks for the follow up!

Let's have a separate file for each page and regarding the laguage selection let's use a combination of localStorage (to remember the user option) and laguage in the url.

E.g. If the user chooses spanish, let's save "es" as prefered language and everytime the user logs into the app, they will be redirected to /es/url-route

Please let me know if it makes sense.