senternet-site-multilingual

Create a central i18n module with a Language type, a copy object keyed by locale, and a React Context provider. Add URL-prefixed routes per locale (e.g. /es/, /fr/), detect language from the URL prefix, and render all copy through a useCopy hook.

Generate one link rel="alternate" per locale plus an x-default entry pointing at the English URL, built dynamically from the locale list. Each localized page must reference its own locale canonical, and hreflang targets must be reciprocal across all pages.

Yes. The Next.js track uses a dynamic [locale] segment with generateStaticParams, a library like next-intl for messages, middleware.ts for locale detection, and metadata alternates.languages for hreflang instead of a React Context provider and prerender loop.

No. An indexable locale is a complete content release. Keep incomplete locales out of the published locale list, routes, prerendering, hreflang, and sitemaps until every indexable route has full translated copy, metadata, and schema labels.

Maintain a list of RTL locale codes and set document.documentElement.dir to rtl and lang to the active locale in an effect. Arabic, Hebrew, Persian, and Urdu require dir="rtl" on the html element for correct layout.

This happens when locale routes are prerendered or indexed before translations are complete, or when components hardcode default-language strings. Run regression tests that compare localized main content against the English version and fail on identical text.