Discuss app-wide localization support #266

Summary

Discuss whether maintainers want app-wide localization for OrgExplorer. The frontend currently uses hard-coded English text and has no shared i18n mechanism or translation resources. This is a separate proposal, not a requirement for the 404-page change in PR #265.

Proposed scope, if maintainers approve

• Select a shared localization approach and establish translation resources and language selection/fallback behavior.
• Plan migration of user-visible text across the frontend, including src/pages/NotFoundPage.jsx, rather than introducing an isolated solution for the 404 page.
• Add tests for the chosen localization behavior and document how contributors add or update translations.

Acceptance criteria

• Maintainers decide whether app-wide localization is in scope and record the decision.
• If approved, define the implementation approach and migration plan, including the 404 page and other existing pages.

Context: #265
Discussion: #265 (comment)
Requested by: @RounakKumarAgarwal, who offered to help if maintainers want to proceed.