Localization Guides
Each guide walks through a specific localization scenario end-to-end - from configuring a localization engine on Lingo.dev to shipping translated output in production. Every guide assumes you have an organization and at least one localization engine configured.
How Guides Work#
Every product has different localization surfaces. A web app needs translated UI strings. An API needs localized responses. A documentation site needs translated Markdown files. Each surface connects to the same localization engine, but the integration pattern differs.
These guides cover seven integration patterns:
| Surface | What gets localized | Integration method |
|---|---|---|
| Translation API | Key-value data, dynamic content | HTTP API calls |
| Web apps | UI strings, component text | CLI + framework integration |
| Mobile apps | iOS .strings, Android .xml | CLI + mobile build pipeline |
| iOS apps | Xcode String Catalogs .xcstrings | CLI + GitHub Actions |
| Android apps | Android strings.xml | CLI + GitHub Actions |
| Next.js with Markdoc | Markdoc pages and JSON UI strings | CLI + GitHub Actions |
| Rails with i18n | Rails config/locales YAML | CLI + GitHub Actions |
| Emails | Transactional and marketing templates | API or CLI depending on template format |
| Static content | Markdown, JSON, YAML files | CLI with file-based translation |
| CI/CD workflows | All of the above, automated | GitHub Actions, GitLab CI, Bitbucket Pipelines |
Prerequisites
All guides require an API key and a configured localization engine. If you haven't set these up yet, start with the documentation.
Choose Your Guide#
Translation API
Send key-value data to the localization API and get translations back programmatically
Web App
Localize React, Next.js, and other web frameworks using the CLI
Mobile App
Localize iOS and Android applications with per-locale model selection
iOS with String Catalogs
End-to-end Xcode .xcstrings localization with CLI and GitHub Actions
Android with strings.xml
End-to-end Android XML localization with CLI and GitHub Actions
Rails with i18n
End-to-end Rails config/locales YAML localization with CLI and GitHub Actions
Emails
Translate transactional and marketing email templates with brand voice applied
Static Content
Translate Markdown, JSON, and other static files in your repository
CI/CD Workflows
Automate localization on every push with GitHub Actions, GitLab CI, or Bitbucket
Engine Setup with MCP
Configure a localization engine using AI coding assistants through the Lingo.dev MCP server
Jira Triage
Automatically triage Jira tickets for localization relevance with AI-powered suggestions