Description
The FAQ page calls translation keys like t('faq.q1'), but no top-level "faq" block exists in the locale files. Since t() returns the key string when missing, the fallback text is never used. As a result, the page renders raw text like faq.q1 and faq.a1 instead of real FAQ content.
Evidence
- Missing FAQ keys used in
app/faq/page.tsx (line 23)
t() returns the key path when no translation exists in context/TranslationContext.tsx (line 164)- No locale file contains a top-level
"faq" section
Suggested Fix
- Add
faq.q1 through faq.a8 (or however many FAQ entries exist) to locales/en.json
- Mirror those keys in the other locale files, or rely on English fallback for missing translations
- Alternatively, update
app/faq/page.tsx to use t('faq.q1', { defaultValue: '...' }) so a sensible fallback is shown even if keys are missing
Description
The FAQ page calls translation keys like
t('faq.q1'), but no top-level"faq"block exists in the locale files. Sincet()returns the key string when missing, the fallback text is never used. As a result, the page renders raw text likefaq.q1andfaq.a1instead of real FAQ content.Evidence
app/faq/page.tsx(line 23)t()returns the key path when no translation exists incontext/TranslationContext.tsx(line 164)"faq"sectionSuggested Fix
faq.q1throughfaq.a8(or however many FAQ entries exist) tolocales/en.jsonapp/faq/page.tsxto uset('faq.q1', { defaultValue: '...' })so a sensible fallback is shown even if keys are missing