adhit-r/fairmind

Internationalization: Add Multi-language Support

Open

#104 opened on Nov 5, 2025

View on GitHub
 (5 comments) (0 reactions) (1 assignee)Python (12 forks)auto 404
enhancementfrontendgood first issuehelp wanted

Repository metrics

Stars
 (9 stars)
PR merge metrics
 (PR metrics pending)

Description

Description

Add multi-language support (i18n) to the FairMind platform to make it accessible to users worldwide.

Why This Is a Good First Issue

  • High impact feature
  • Can be implemented incrementally
  • Good learning opportunity for i18n
  • Clear scope and requirements
  • Well-documented patterns available

Current State

  • Application is English-only
  • No internationalization infrastructure
  • Text is hardcoded in components

Goals

  1. Set Up i18n Infrastructure

    • Choose i18n library (next-intl, react-i18next, etc.)
    • Configure translation system
    • Set up language detection

  2. Extract Text

    • Identify all user-facing text
    • Extract to translation files
    • Organize by feature/page

  3. Implement Language Switching

    • Language selector component
    • Persist language preference
    • Update UI dynamically

  4. Initial Languages

    • English (default)
    • Spanish
    • French
    • Additional languages as needed

Getting Started

  1. Prerequisites

    • React/Next.js knowledge
    • Understanding of i18n concepts
    • Familiarity with translation workflows

  2. Recommended Library

    • next-intl (recommended for Next.js)
    • Or react-i18next with next-i18next

  3. Files to Modify

    • apps/frontend-new/src/app/ - Page files
    • apps/frontend-new/src/components/ - Component files
    • Create messages/ directory for translations

  4. Implementation Steps

    • Install i18n library
    • Configure Next.js for i18n
    • Extract text to translation files
    • Add language switcher component
    • Test language switching
    • Add additional languages

Acceptance Criteria

  • i18n infrastructure set up
  • All user-facing text extracted
  • Language switcher implemented
  • At least 2 languages supported
  • Language preference persisted
  • Documentation updated

Resources

Related

Related to parent issue #133 (Platform Enhancements & User Experience)

Labels

enhancement, help wanted, good first issue, frontend

Contributor guide

Research direction
Explore the current codebase to identify all user facing hardcoded strings, then set up next intl and extract them into translation files.
Tech stack
javascripttypescriptreactnextjs
Domain
frontend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
ReactNext.jsi18n
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70