Summary
Multi-language support isn't formally offered — the tester was already viewing the site in Turkish, so partial i18n exists, but it's not exposed as a first-class feature.
Problem
A non-English-speaking builder pointed out that the site doesn't offer explicit language options. Their browser's auto-translate appears to be picking up Turkish (labels showed as İnşaatçılar / Projeler / Olaylar / Aktivite), but there's no in-app language selector, and translations aren't quality-controlled.
Expected behavior
- Add a language selector in Settings (and optionally in the header user menu) with a small starter set: English, Turkish, Spanish, Russian, Chinese (adjust based on user demographics).
- Wire strings through an i18n library (
react-i18next / next-intl) so text is pulled from locale files, not hardcoded.
- Ship English as canonical; accept community PRs for other locales.
- Persist the choice per-account (fall back to browser locale for signed-out users).
Source
Telegram — @rykc22.tg (screenshot review, 11:16 AM)
Summary
Multi-language support isn't formally offered — the tester was already viewing the site in Turkish, so partial i18n exists, but it's not exposed as a first-class feature.
Problem
A non-English-speaking builder pointed out that the site doesn't offer explicit language options. Their browser's auto-translate appears to be picking up Turkish (labels showed as İnşaatçılar / Projeler / Olaylar / Aktivite), but there's no in-app language selector, and translations aren't quality-controlled.
Expected behavior
react-i18next/next-intl) so text is pulled from locale files, not hardcoded.Source
Telegram — @rykc22.tg (screenshot review, 11:16 AM)