Contents
Opter builds a market-leading transport management system. For years, its documentation was translated twice a year. Source content was written in MadCap Flare, exposed for translation through Lingo, sent to an agency for human translation, returned, re-imported, and built.
Flare now flows directly into a TMS-backed automated translation pipeline with optional human validation, and back into Flare. Translations that used to land twice a year now land daily.
But the real story is not the pipeline. It is how the roles and responsibilities changed when translation stopped setting the calendar and became part of the everyday documentation workflow.
Takeaways
Participants will leave with concrete lessons from turning a manual Flare/Lingo translation process into a daily automated workflow.
Prior knowledge
Participants will benefit from having a basic understanding of technical documentation and localization workflows. Familiarity with authoring tools, translation management systems, or translation agencies will help, but no deep technical or programming knowledge is required.