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

未关闭
#268 1 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

维护者通常 1 天内回复

@amankv1234 已经在做这个了。

开始于 2026年10月15日。

评估

难度
5/5
预计耗时
一周以上
新手友好度
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 分钟
30 天内合并 PR
2

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

AOSSIE-Org/OrgExplorer 的其他 Issue

查看 AOSSIE-Org/OrgExplorer 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。