OpenText TeamSite - LiveSite Content Services - LionBridge Integration and Automation

Common Integration Use Cases Between OpenText TeamSite - LiveSite Content Services and LionBridge

1. Automated Website Translation Workflow for Multilingual Publishing

Direction: OpenText TeamSite - LiveSite Content Services to LionBridge and back

When marketing teams publish new web pages, product updates, or campaign content in OpenText TeamSite - LiveSite Content Services, the content is automatically sent to Lionbridge for translation and localization. Once translated, the localized versions are returned to TeamSite for review and publishing.

• Reduces manual copy and paste work across language teams
• Speeds up launch of multilingual websites and portals
• Ensures consistent content structure across all language variants

2. Localized Personalization for Regional Digital Experiences

Direction: Bi-directional

OpenText TeamSite - LiveSite Content Services can deliver personalized content based on user location, language preference, or market segment, while Lionbridge provides the translated content variants needed for each region. The integration ensures that personalized content blocks are available in the correct language before being rendered on the site.

• Improves relevance of digital experiences for global audiences
• Supports regional campaigns with language-specific messaging
• Helps maintain brand consistency across markets

3. Translation of Product and Service Content for Global Launches

Direction: OpenText TeamSite - LiveSite Content Services to LionBridge

Product launch pages, service descriptions, and promotional assets managed in OpenText TeamSite - LiveSite Content Services can be routed to Lionbridge for translation as part of a launch workflow. This is especially useful for enterprises rolling out products across multiple countries with tight deadlines.

• Aligns localization with launch schedules
• Reduces delays caused by manual translation coordination
• Supports simultaneous go-live across multiple markets

4. Governance and Review Workflow for Localized Content

Direction: Bi-directional

After Lionbridge completes translation, localized content can be sent back to OpenText TeamSite - LiveSite Content Services for in-context review by regional marketing, legal, or compliance teams. Approved content is then published to the live site.

• Improves quality control before content goes live
• Supports legal and regulatory review in local markets
• Creates a controlled publishing process for multilingual content

5. Translation of Reusable Content Components and Templates

Direction: OpenText TeamSite - LiveSite Content Services to LionBridge

Reusable content components such as banners, call-to-action text, navigation labels, and footer content can be extracted from OpenText TeamSite - LiveSite Content Services and sent to Lionbridge for translation. This ensures that shared components are localized once and reused consistently across pages and microsites.

• Reduces duplicate translation effort
• Improves consistency across digital properties
• Speeds up updates to shared interface elements

6. Multilingual Content Updates for Regulatory and Policy Pages

Direction: OpenText TeamSite - LiveSite Content Services to LionBridge

For industries such as financial services, healthcare, or manufacturing, policy pages and regulatory disclosures often need frequent updates in multiple languages. OpenText TeamSite - LiveSite Content Services can trigger translation requests to Lionbridge whenever source content changes, ensuring all language versions stay synchronized.

• Supports compliance with local language requirements
• Reduces risk of outdated translated legal content
• Improves auditability of content changes and approvals

7. Centralized Localization Pipeline for Global Content Operations

Direction: Bi-directional

OpenText TeamSite - LiveSite Content Services acts as the content source system, while Lionbridge serves as the localization engine within a centralized translation workflow. Content status, translation progress, and completion updates can be exchanged between the systems to give content managers visibility into the full lifecycle.

• Provides operational transparency for content teams
• Helps prioritize high-value content for translation
• Enables better planning for global content releases