Skip to content

feat: implement internationalization for all missing i18n keys #764

@Anuoluwapo25

Description

@Anuoluwapo25

The i18n framework is set up with English keys, but some newer UI elements may not be using translation keys.\n\nAction:\n- [ ] Audit all hardcoded strings in the frontend\n- [ ] Extract all strings to src/locales/en.json\n- [ ] Add i18next-scanner to CI to detect missing translation keys\n- [ ] Document translation workflow for contributors\n- [ ] Add pseudo-locale testing to catch untranslated strings

Metadata

Metadata

Assignees

No one assigned

    Labels

    frontendReact/TypeScript UI workgood first issueGood for newcomersi18nInternationalization and localization

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions