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 |
| Emails | Transactional and marketing templates | API or CLI depending on template format |
| Static content | Markdown, JSON, YAML files | CLI with file-based translation |
| CMS content | Headless CMS entries and fields | API with CMS webhooks |
| 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
Emails
Translate transactional and marketing email templates with brand voice applied
Static Content
Translate Markdown, JSON, and other static files in your repository
CMS Content
Connect a headless CMS and localize content through the API
CI/CD Workflows
Automate localization on every push with GitHub Actions, GitLab CI, or Bitbucket