Workflow Examples

Overview

These workflow examples show how different teams use Antinium to create and translate documents efficiently.

Workflow 1: Product Documentation

Scenario: A product team needs to create user guides in English and Spanish.

1. Create the English version in Antinium
2. Enable translation memory for consistency
3. Translate the entire document to Spanish
4. Review the Spanish translation using multilingual view
5. Edit any sections that need adjustment
6. Share both versions with the team for review
7. Export both versions as PDFs
8. When updating the English version, re-translate changed sections

Workflow 2: Marketing Content

Scenario: Marketing team creates blog posts and needs them in multiple languages.

1. Write the blog post in English
2. Use "Marketing" localization style for translation
3. Translate to target languages (e.g., Spanish, French, German)
4. Review each translation for brand voice and tone
5. Adjust cultural references and idioms as needed
6. Share with native speakers for final review
7. Export and publish each language version

Workflow 3: Internal Policies

Scenario: HR team needs to translate company policies for a multilingual workforce.

1. Create the policy document in the source language
2. Use "Formal" or "Legal" localization style
3. Translate to all required languages
4. Use multilingual view to ensure consistency
5. Have legal/compliance team review each translation
6. Share final versions with all employees
7. Store all versions in a shared workspace folder

Workflow 4: Technical Documentation

Scenario: Developer documentation needs to be available in multiple languages.

1. Write technical documentation in English
2. Use "Technical" localization style
3. Enable translation memory for consistent terminology
4. Translate code comments and documentation
5. Verify code examples and technical terms are correct
6. Have technical reviewers check each language version
7. Export as HTML for web publishing

Workflow 5: Collaborative Translation

Scenario: Multiple team members collaborate on translating a large document.

1. Create the source document
2. Share the document with translation team members
3. Assign different sections to different translators
4. Each translator translates their assigned sections
5. Use comments to ask questions and provide feedback
6. Reviewer checks translations using multilingual view
7. Make final edits and approve translations
8. Export the final multilingual document

Workflow 6: API-Driven Automation

Scenario: Automate translation of content from a CMS or other system.

1. Set up webhook endpoint to receive content
2. When new content is created, call Antinium API
3. Translate content to target languages via API
4. Receive webhook notification when translation completes
5. Fetch translated content via API
6. Update your CMS with translated versions
7. Publish all language versions

Tips for Each Workflow

Related Topics

• Best Practices - General guidelines
• Translation in the Editor - Translation features
• API Overview - Automate workflows