[fauztech05]

Overview

This PR introduces internationalization scaffolding to the frontend using react-i18next, moving user-facing strings out of components and wiring up the i18n provider at app startup.

Related Issue

Closes #

Changes

🌐 Internationalization Setup

• [MODIFY] frontend/package.json / package-lock.json

  • Adds react-i18next (and its i18next peer) as dependencies.

• [MODIFY] frontend/src/main.tsx

  • Initializes the i18n instance before the app renders.

• [MODIFY] frontend/src/App.tsx

  • Wires the i18n provider into the component tree.

🧩 Component String Extraction

• [MODIFY] frontend/src/pages/BountyList.tsx, frontend/src/pages/BountyDetail.tsx, frontend/src/pages/About.tsx, frontend/src/components/Layout.tsx, frontend/src/components/BountyCard.tsx
  • Replace hard-coded English UI strings with translation keys via useTranslation().

Verification Results

grep -rn ">[A-Za-z][^<{]*<" frontend/src/pages frontend/src/components
# no hard-coded user-facing strings remain in the modified components

Acceptance Criteria	Status
No hard-coded user-facing strings remain in components	✅ Verified via grep on modified files
npm run lint, typecheck, test, build pass in frontend/	⏳ To be confirmed in CI
PROGRESS.md entry added	⏳ Pending
PR description includes Closes #<this issue>	✅

Closes #170