i18n foundation: next-intl, locale routing, RTL support, language switcher
Wire up next-intl on the App Router with locale-prefixed routes (/en/..., /de/..., /ar/...) and a cookie-based fallback so signed-in users keep their preferred language across devices. Add locale column to profiles (default null = Accept-Language fallback) and default_locale on projects (controls the public-surface default for non-signed-in visitors).
Language switcher in the user account menu and on every public page footer. RTL support primitives: <html dir="rtl"> when locale is Arabic/Hebrew/Persian/Urdu, Tailwind logical properties pass over physical ones for new components, audit existing components for left/right hardcodes (separate follow-up card if heavy). <html lang> attribute set on every page; hreflang link tags emitted on the public surface for SEO.
Extract all currently-hardcoded UI strings into messages/en.json so the build proves the catalog works end-to-end. Date/number/plural formatting goes through ICU MessageFormat (next-intl built-in). Out of scope: actually translating to non-English locales (separate card), translating user-generated content like post bodies (separate card), translating Supabase auth email templates (separate card).
Comments (0)
No comments yet.
Sign in to leave a comment.
