Normal view

Native AI translation in TMGMT: How to automate workflows without losing context or layout integrity

Hi everyone,

If you’ve managed large multilingual Drupal sites, you know the TMGMT module is a good way to go, but the actual translation process (especially with AI) can still feel a bit disconnected from the site's context.

We built an integration that lives directly inside TMGMT. The goal was to solve three specific issues:

  1. Context: Choosing between 'Faithful', 'Fluid', or 'Creative' styles based on the content type.
  2. Consistency: Using translation memories and glossaries so the AI doesn't hallucinate brand terms.
  3. Layout: Ensuring the translated strings don't break your site's design.

We’re hosting a live, hands-on session on May 7th at 11 AM CEST to show the technical setup and how it handles complex nodes.

Registration (Free): https://laratranslate.com/webinar-lara-translate-sparkfabrik

Roberto Peruzzo from Sparkfabrik will be there to dive into the dev side of things. If you have questions about TMGMT provider configurations or AI localization workflows, feel free to drop them here or join us live!

submitted by /u/LaraTranslate
[link] [comments]

Lara Translate integrated with Drupal TMGMT (open module) for AI translations with style + glossary + TM

Lara Translate integrated with Drupal TMGMT (open module) for AI translations with style + glossary + TM

Hey folks, sharing something we just shipped for Drupal multilingual teams.

I work on Lara Translate, and together with SparkFabrik, we built a TMGMT provider that lets editors translate Drupal content with AI directly in Drupal, instead of copying and pasting into external tools.

https://preview.redd.it/30kdql9hs2gg1.png?width=750&format=png&auto=webp&s=c5f04519ee57b4040bf0b3ffad488dc9266bc8c1

What it does (in plain terms)

  • Use Lara Translate as a translation provider in TMGMT
  • Send nodes, paragraphs, and other entities to translation
  • Automatically pull translations back into Drupal with job statuses (in progress, completed, errors)
  • Keep the full Drupal workflow: roles, permissions, revision history, approvals, governance

On the Lara side, the integration exposes:

  • Style control (Faithful / Fluid / Creative)
  • Glossaries + Translation Memories
  • Ambiguity flags + explanations to help reviewers focus on the risky bits

(Also, outside Drupal, Lara Translate supports broad document workflows too, including 70+ file types if your team translates CMS content and files in parallel.)

Who this is for

If your multilingual Drupal site is “serious” (universities, public institutions, enterprise, regulated, or brand-sensitive content), you probably already know the pain:

  • tone drifting across locales
  • terminology inconsistencies across hundreds of nodes
  • translations living in spreadsheets and inboxes instead of your CMS

Quick setup steps

  1. Install TMGMT + the Lara Translate Provider module
  2. Add your Lara API credentials in TMGMT Providers
  3. Set defaults (style, job settings), then run a small pilot (news or low-risk content)
  4. Scale out, keep humans in the loop for high-impact pages

Links

We’re also planning a free webinar in Q2 2026 with SparkFabrik (date TBA) to show real workflows in TMGMT.

I’d love feedback

If you’ve implemented AI translation in Drupal already:

  • What broke first for you: quality, workflow, governance, SEO, something else?
  • Do you prefer “AI in the CMS” or “translation platform + connector” setups, and why?

Happy to answer technical questions too.

submitted by /u/LaraTranslate
[link] [comments]
❌