W31 Product Update: Share glossaries, rulesets, and brand voices across engines
Glossaries, rulesets, and brand voices now live at the organization level and attach to any engine.
Build a glossary, a ruleset of linguistic rules, or a brand voice once, then attach it to any engine that needs it. Edit a shared asset and every engine it's attached to picks up the change. A new engine no longer starts from an empty configuration: attach what you already have and it inherits it.
Also this week:
Take over a translation waiting on external review. When a job is parked on an external professional reviewer, an authorized member of your own team can open the pending review in the dashboard and submit the decision, so the job continues instead of waiting on the external round trip.
A runnable example repo for every framework. Each is a real project with .lingo/config.json and translations committed – clone it, run lingo link, and push: iOS, Android, Flutter, React + Vite, Next.js, Rails, Laravel, Markdown, Markdoc, OpenAPI, and TypeScript modules.
Full changelog: lingo.dev/changelog


Replies