Summary
Trivela targets the global Stellar ecosystem but all UI text is hardcoded in English. Adding an i18n framework now (before the string count grows) will enable the community to contribute translations and reach non-English-speaking Stellar users — a significant untapped audience.
Problem
- All UI strings are hardcoded in JSX components
- No i18n framework configured
- No translation files or contributor workflow for adding languages
- Retro-fitting i18n after the fact is significantly more costly
Acceptance Criteria
References
frontend/src/ — all JSX components with UI strings
CONTRIBUTING.md
- react-i18next
Summary
Trivela targets the global Stellar ecosystem but all UI text is hardcoded in English. Adding an i18n framework now (before the string count grows) will enable the community to contribute translations and reach non-English-speaking Stellar users — a significant untapped audience.
Problem
Acceptance Criteria
i18next+react-i18nexttofrontend/Landing.jsx,Header.jsx,CampaignDetail.jsx,CreateCampaign.jsx,About.jsx,ErrorBoundary.jsxintofrontend/src/locales/en.jsoni18next-browser-languagedetector(auto-detect from browser)Header(show when > 1 language available)es.json— Spanish — with machine-translated strings marked for community review)CONTRIBUTING.mden.jsonmust have all keys present (fail if new string added to code without translation key)References
frontend/src/— all JSX components with UI stringsCONTRIBUTING.md