Complete Pipeline Documentation

Internationalization & Localization
Pipelines

The definitive technical reference for building production-grade i18n/l10n pipelines. Covering locale negotiation, framework adapters, RTL support, CI/CD sync, catalogue governance, Unicode text handling, form input, and locale-aware SEO.

Written for full-stack developers, UX engineers, product teams, and localization managers who need deterministic, cache-aware, edge-ready internationalization that scales.

🌐 Core i18n Architecture ⚛️ Framework Integrations 🔄 CI/CD Workflows
105 Guides
3 Areas
7 Frameworks

Start Here

Hand-picked deep dives that solve the problems teams hit first when shipping a multi-locale product — and the ones they hit again at the second dozen locales.

Core Architecture

ICU MessageFormat for Complex Plurals

Write nested plural and select messages that survive extraction, translation, and re-import without escaping errors.

Read the guide → Core Architecture

Pluralization in Arabic & Slavic Languages

Map CLDR plural categories to real message strings so counts read naturally in languages with up to six plural forms.

Read the guide → Framework i18n

Next.js App Router i18n Middleware

Configure locale-aware middleware in the App Router so routing, redirects, and negotiation all resolve at the edge.

Read the guide → Core Architecture

Localization Testing & Pseudolocalization

Generate an accented, expanded pseudo-locale and catch hardcoded strings, clipped buttons and missing direction handling before a word is translated.

Read the guide → Core Architecture

String Catalog Governance

Key naming, namespace ownership and deprecation windows that keep a catalogue useful after two years of copy edits.

Read the guide → Framework i18n

Locale-Aware SEO & hreflang

Self-referencing canonicals, reciprocal hreflang and a working x-default — the five signals that decide whether your localized pages are found at all.

Read the guide → Workflows & CI/CD

Monorepo i18n Package Architecture

One runtime, one versioned catalogue, one extraction — the package boundaries that stop three applications translating the same string three times.

Read the guide → Framework i18n

Nuxt i18n Module Setup

Treat the module as the route generator it is: pick a strategy before publishing URLs, and keep detection off already-prefixed paths.

Read the guide → Core Architecture

Unicode Text Handling & Collation

Normalize on write, sort with a collator rather than Array.sort, and measure length in grapheme clusters — the four operations behind most user-text bugs.

Read the guide → Framework i18n

Internationalizing Forms & Input

Country decides structure, locale decides presentation: per-country address schemas, E.164 phone storage, and number parsing the platform does not give you.

Read the guide → Core Architecture

Intl Polyfills & ICU Data Loading

A slim ICU build answers every locale in English and never errors. Detect the data by formatting, and load a polyfill only for the readers who need it.

Read the guide → Workflows & CI/CD

Connect Crowdin to GitHub Pull Requests

Wire the Crowdin API into your PR flow so translation updates land as reviewable commits instead of manual uploads.

Read the guide → Workflows & CI/CD

Fail the Build on Untranslated Keys

Add a GitHub Actions gate that blocks merges when required locales are missing keys, keeping every release fully localized.

Read the guide →

Where to start

A hundred and five guides 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.

🌐

Core i18n Architecture & Locale Negotiation

The foundational layer

How to resolve a reader's locale predictably, work with ICU message format, handle CLDR pluralization, build fallback chains that degrade gracefully, format dates and numbers with the native Intl API, handle Unicode text correctly, and govern and test the catalogue behind all of it.

Explore Core Architecture →
⚛️

Frontend Framework i18n & Component Routing

Framework-specific integrations

Framework-specific i18n patterns for React, Next.js, Vue 3, Nuxt, Angular, SvelteKit and Astro — with type-safe hooks, middleware routing, SSR hydration strategies, and the canonical and hreflang annotations that make localized routes findable — plus the forms and inputs where localized data actually enters your product.

Explore Framework i18n →

What You'll Learn

Pipeline-first i18n for teams that ship globally

⚡

Edge-Level Locale Resolution

Implement deterministic locale negotiation at the CDN edge before any application hydration occurs, eliminating flash-of-unlocalized-content.

🔐

Type-Safe Translation Keys

Enforce compile-time validation of all translation keys using TypeScript declaration merging and AST-based extraction pipelines.

🌍

RTL & Bidirectional Layouts

Build direction-agnostic UIs using CSS logical properties and PostCSS plugins, enabling seamless Arabic and Hebrew localization.

📊

CLDR Pluralization Rules

Handle complex plural forms across Arabic, Slavic, and Asian languages using ICU MessageFormat and standardized CLDR data.

🚀

CI/CD Pipeline Automation

Automate string extraction, TMS sync, validation, and deployment gating using GitHub Actions with idempotent, hash-verified workflows.

💱

Currency & Number Formatting

Implement market-specific currency display, decimal separators, and financial rounding using native Intl APIs with cached formatter instances.

The i18n Pipeline

Five non-negotiable engineering principles for production-grade localization

01

Build-Time Extraction

Extract strings via AST parsing at build time, not runtime scanning. Guarantees catalog completeness and eliminates client-side parsing overhead.

02

Edge Locale Resolution

Resolve locale at the CDN edge before application boot. Prevents FOUC and reduces redirect latency to zero.

03

Immutable Catalogs

Version translation artifacts as immutable, semantically versioned bundles. Enables atomic rollbacks and deterministic cache invalidation.

04

Automated CI Gates

Block malformed ICU syntax, placeholder drift, and missing keys from reaching staging with automated validation pipelines.

05

Cache-Aware Fallbacks

Implement stale-while-revalidate fallback chains that degrade gracefully without triggering origin fetch storms or 404 cascades.