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

オープン
#268 コメント 1 件 リアクション 0 件 担当者 1 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

@amankv1234 がすでに取り組んでいます。

2026年10月15日 から。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
25/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
javascript, react

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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
主要言語
JavaScript
スター
53
フォーク
182
平均マージ
18分
マージ済み PR(30日)
2

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

AOSSIE-Org/OrgExplorer のほかの issue

AOSSIE-Org/OrgExplorer の issue をすべて見る

似ている issue

JavaScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。