Quick Answer
A strong Drupal translation workflow uses Drupal core multilingual modules for language structure, then adds a review workflow around the content that actually changes. Start with Language, Content Translation, Interface Translation, and Configuration Translation. Use TMGMT or a translation connector when content needs to move between Drupal, translators, and a translation management system.
| Workflow Layer | Drupal Feature | What It Controls |
|---|---|---|
| Site languages | Language module | Available languages and negotiation |
| Editorial content | Content Translation | Nodes, taxonomy, blocks, media fields |
| Admin and UI text | Interface Translation | Drupal and module UI strings |
| Site configuration | Configuration Translation | Menus, views, content type labels |
| External workflow | TMGMT/connectors | Translation jobs, vendors, AI, review |
1. Enable Drupal Core Multilingual Modules
Drupal's official multilingual documentation recommends enabling the core modules that match the kind of content you need to translate. Content Translation is the main module for translating content entities such as nodes, comments, custom blocks, taxonomy terms, and user accounts.
The usual starting stack:
- Language: adds languages and language negotiation.
- Content Translation: translates content entities and fields.
- Interface Translation: translates Drupal interface strings.
- Configuration Translation: translates configuration such as menus, views, and content type labels.
Official reference: Drupal multilingual guide.
2. Decide Which Fields Are Translatable
Do not make every field translatable by default. Field-level translation is powerful, but it can create governance problems if teams translate IDs, shared assets, or technical metadata that should remain global.
Good candidates for translation:
- Title and body fields
- Meta titles and descriptions
- Taxonomy labels shown to users
- Image alt text and captions
- CTA labels and landing page copy
Usually keep these shared:
- Internal IDs
- Canonical references
- Analytics tags
- System-only fields
- Fields that drive business logic
3. Add Review States
For editorial teams, a useful Drupal translation workflow has separate states for source and target content:
- Draft source content.
- Approve source content for translation.
- Send target languages to translators or AI.
- Review translated fields in Drupal.
- Publish only the approved translation.
- Reopen translation jobs when source content changes.
This avoids the common failure mode where a source page changes but old translations stay published with outdated claims.
4. Use TMGMT When Drupal Is Not the Only System
Drupal's Translation Management Tool ecosystem is useful when translations need to move through vendors, agencies, AI workflows, or external TMS platforms. Use it when you need job tracking, translation memory, glossary enforcement, or approval states outside Drupal itself.
For software teams, connect Drupal content translation to the same terminology and translation memory used by your app, docs, and marketing site. That prevents product terms from drifting between CMS pages and application UI.
5. Add Multilingual SEO Checks
Before publishing translated Drupal pages, check:
- Each translated page has a localized title and meta description.
- hreflang annotations point to the correct language versions.
- URL aliases are translated where appropriate.
- Canonicals do not point every language back to English.
- Image alt text is localized.
- Internal links point to the matching language where possible.
Frequently Asked Questions
What is the best Drupal translation workflow?
The best Drupal translation workflow combines core multilingual modules with a clear editorial review process. Use Content Translation for page content, Configuration Translation for site labels, Interface Translation for UI strings, and TMGMT or a connector when translators, vendors, or AI systems need to participate.
Does Drupal support multilingual content out of the box?
Yes. Drupal core includes multilingual capabilities, including modules for language setup, content translation, interface translation, and configuration translation. Complex review and vendor workflows usually need additional configuration or modules.
Should I use TMGMT for Drupal translation?
Use TMGMT when Drupal content needs structured translation jobs, vendor handoff, AI translation, or translation memory. If your site has only a few pages and one editor, core Content Translation may be enough.
