Lingo.dev
Oct 9, 2026
W40 Product Update: Localization in the tools you already use
Why it works
- Lead with the overall capability and its practical benefit before explaining the individual integrations.
- Organize technical details by workflow so readers can find the section relevant to their tools.
- Close with a direct path to try the feature, then offer the changelog for readers who want more detail.
How it is built
- Headline with capability
- Benefit overview
- CLI workflow details
- GitHub app details
Email copy
You can now connect content sources to your localization engines in Studio, translate content with your team's glossary, rules, and brand voice, and write translations back to your repositories, CMSs, or help centers. Connect GitHub, Payload CMS, or Zendesk Help Center, or submit content through the CLI and API. Each source uses the localization engine you choose, with your team's glossary, rules, and brand voice. Product and content teams submit content from their own tools, while the localization team runs the localization infrastructure. The CLI. Engineers use lingo push to submit source files through the localization engine's configured pipeline. lingo pull writes the completed translations to local target files on the same machine and checkout. Studio lists each submission with its status by language. The GitHub App. When source files change on the default branch, the app translates the changes and opens a pull request with the translated files. Enable the pull request workflow to commit translations directly to a pull request branch. Require approval before automatic runs, or use /lingo translate to request specific files and languages. CMSs and help centers. Select the content and target languages, and Lingo.dev writes the translations back to Payload or Zendesk under each locale. Sync translates only new or changed source content. Payload can start runs automatically when content changes; Zendesk runs start manually. Each run uses the localization engine's configured pipeline, including review where enabled. The API. The Sync API returns one target language in the response. The Async API accepts multiple target languages and delivers each completed translation separately. Both apply the localization engine's glossary, rules, brand voice, and model settings. Async jobs also run the configured optional pipeline stages, including native-speaker proofreading where enabled. The Sync API skips those stages. Open Studio → All integrations to connect GitHub, a CMS, or a help center. Read the full changelog → – Veronica Lingo.dev · San Francisco, CA Unsubscribe