[FEATURE]: feat: Implement i18n (Internationalization) support across the entire project

Aperta
#268 1 commento 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@amankv1234 ci sta già lavorando.

Dal 15/10/2026.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
javascript, react

Direzione di ricerca

Start by surveying the affected src/pages/ and src/components/ directories, including SettingsPage, OverviewPage, and the Navbar/Header, to inventory user-facing strings. Review the proposed i18next, react-i18next, and language-detection setup before planning the work. Done means strings use translation keys, the language switcher works, and the selected language persists after reload.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement
Feature and its Use Cases

Overview

Currently, OrgExplorer does not support multiple languages. All text strings are hardcoded directly into the React components (e.g., SettingsPage, OverviewPage, etc.). To make the platform globally accessible and user-friendly for non-English speakers, we need to introduce internationalization (i18n).

Goal

Implement a complete i18n setup across the entire application using a library like react-i18next. This will lay the foundation for supporting multiple languages and ensure all hardcoded text is moved to translation files.

Proposed Solution

  1. Setup i18n Library: Install and configure i18next and react-i18next.
  2. Create Locales Structure: Create a src/locales/ directory with JSON files for different languages (starting with English en.json as the base).
  3. Extract Hardcoded Strings: Go through all components, pages, and hooks to replace hardcoded strings with the useTranslation() hook (e.g., replace "Settings" with t('settings.title')).
  4. Language Switcher UI: Add a simple Language Switcher component in the navbar or settings page to allow users to toggle between languages.
  5. Persist Language Choice: Save the selected language in localStorage or IndexedDB so the preference is remembered across sessions.

Affected Areas

  • Entire src/pages/ directory
  • Entire src/components/ directory
  • Navbar / Header
  • Any utility or service that displays user-facing messages

Technical Details

  • Recommended packages: i18next, react-i18next, i18next-browser-languagedetector
  • Base language: English (en)
  • (Optional) We can also add dummy translations for a second language (e.g., Hindi hi or Spanish es) to verify the language switching functionality.

Acceptance Criteria

  • react-i18next is successfully set up and configured.
  • No hardcoded English text remains in the UI components.
  • A language switcher component is added and functional.
  • Language preference persists on page reload.
Additional Context

No response

Code of Conduct
  • I have joined the Discord server and will post updates there
  • I have searched existing issues to avoid duplicates
Lingua principale
JavaScript
Stelle
53
Fork
182
Merge medio
18m
PR unite (30g)
2

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di AOSSIE-Org/OrgExplorer

Tutte le issue di AOSSIE-Org/OrgExplorer

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.