The definitive technical reference for building production-grade i18n/l10n pipelines. Covering locale negotiation, framework adapters, RTL support, CI/CD sync, and full-stack localization workflows.
Written for full-stack developers, UX engineers, product teams, and localization managers who need deterministic, cache-aware, edge-ready internationalization that scales.
Hand-picked deep dives that solve the problems teams hit first when shipping a multi-locale product.
Write nested plural and select messages that survive extraction, translation, and re-import without escaping errors.
Read the guide → Core ArchitectureMap CLDR plural categories to real message strings so counts read naturally in languages with up to six plural forms.
Read the guide → Framework i18nConfigure locale-aware middleware in the App Router so routing, redirects, and negotiation all resolve at the edge.
Read the guide → Core ArchitectureUse CSS logical properties and direction-aware assets to flip layouts for Arabic and Hebrew without one-off overrides.
Read the guide → Workflows & CI/CDWire the Crowdin API into your PR flow so translation updates land as reviewable commits instead of manual uploads.
Read the guide → Workflows & CI/CDAdd a GitHub Actions gate that blocks merges when required locales are missing keys, keeping every release fully localized.
Read the guide →The guides are grouped into three areas that follow the work itself — from getting locale handling right, to wiring i18n into your framework, to keeping translations in sync through CI/CD.
The foundational layer
How to resolve a user's locale predictably, work with ICU message format, handle CLDR pluralization, build fallback chains that degrade gracefully, and format dates and numbers with the native Intl API.
Framework-specific integrations
Framework-specific i18n patterns for React, Next.js, Vue 3, Angular, and SvelteKit — with type-safe hooks, middleware routing, and SSR hydration strategies.
Automation & tooling
Translation automation that runs in your pipeline: Crowdin and Weblate integrations, AST-based key extraction, GitHub Actions sync workflows, and pipeline-first i18n orchestration.
Pipeline-first i18n for teams that ship globally
Implement deterministic locale negotiation at the CDN edge before any application hydration occurs, eliminating flash-of-unlocalized-content.
Enforce compile-time validation of all translation keys using TypeScript declaration merging and AST-based extraction pipelines.
Build direction-agnostic UIs using CSS logical properties and PostCSS plugins, enabling seamless Arabic and Hebrew localization.
Handle complex plural forms across Arabic, Slavic, and Asian languages using ICU MessageFormat and standardized CLDR data.
Automate string extraction, TMS sync, validation, and deployment gating using GitHub Actions with idempotent, hash-verified workflows.
Implement market-specific currency display, decimal separators, and financial rounding using native Intl APIs with cached formatter instances.
Five non-negotiable engineering principles for production-grade localization
Extract strings via AST parsing at build time, not runtime scanning. Guarantees catalog completeness and eliminates client-side parsing overhead.
Resolve locale at the CDN edge before application boot. Prevents FOUC and reduces redirect latency to zero.
Version translation artifacts as immutable, semantically versioned bundles. Enables atomic rollbacks and deterministic cache invalidation.
Block malformed ICU syntax, placeholder drift, and missing keys from reaching staging with automated validation pipelines.
Implement stale-while-revalidate fallback chains that degrade gracefully without triggering origin fetch storms or 404 cascades.
