Internationalization moves language and presentation choices to explicit boundaries. A case system can store one timestamp and one reimbursement while showing both to readers in different locales. Its routes and help content may also exist in several languages. The lessons separate message identity, value formatting, text direction, and translation publication so a copy edit cannot change a business record or strand an old link.
Topics in this track
- Message Catalog Contracts and Fallback — Treat translated strings as versioned interface data with stable keys and visible missing-message behavior.
- Currency, Date, and Time-Zone Presentation — Keep canonical values separate from locale-sensitive display and explicit time-zone policy.
- Right-to-Left and Mixed-Direction Content — Declare page direction and isolate unknown text so identifiers and prose remain legible together.
- Localized Routes and Translation Release — Publish language-specific pages without losing identity, old links, or editorial readiness.
Prerequisite paths
Locale and Time-Zone Boundaries; Canonical Route Identity; Static, Server-Rendered, and Client-Rendered Pages.
Neighbor track
Inclusive Interface Engineering.
Practice path
Build Project: localized guide release and check choices in Web Development: inclusive and global delivery quiz.