Skip to content
Trans-Hub LogoTrans-Hub语枢

TRANS-HUB / CONNECTING DIGITAL WORLDS

Many languages.
One shared world.

Give your software, websites, and digital ecosystems a voice in more languages.

Start with public ecosystems, then bring localization to your own product with a private team project. Keep translations, collaboration, and version updates connected.

Explore ecosystemsFor your team
Language assetsCollaborationConnected ecosystems
YOUR ECOSYSTEMSGLOBAL EXPRESSION
ObsidianPLUGIN UI
WebWEBSITE UI
Your contentPROJECT SOURCE
Trans-Hub LogoTRANS-HUBCONNECT · COLLABORATE · EVOLVE
Englishen-US

Turn good ideas
into great work.

简体中文zh-CN

让好想法，
成为好作品。

日本語ja-JP

アイデアを、
素敵な作品へ。

ONE MESSAGE, MANY LANGUAGES · CONCEPT
01 — TRANSLATE. CONNECT. EVOLVE.BUILT FOR DEVELOPERS, TRANSLATION TEAMS & DIGITAL ECOSYSTEMS

01 / A GROWING ECOSYSTEM

One hub. More possibilities.

All ecosystems
Obsidian ecosystem concept: a violet crystal with interlocking plugin modulesConcept illustration
Obsidian

Your plugins. Your language.

Make community plugin features and prompts easier to understand in the tool you already use.

Plugin localizationExplore plugins

Start with an ecosystem you know. Visit its page for current coverage and ways to get started.

02 / KEEP UP WITH CHANGES

Your content changes.
Build on your translations.

See changes alongside existing translations, so your team can compare, revise, and build on earlier work.

One button, a small changeIllustration
In your productExisting Chinese translation
In your product
Create a projectCreate your first project
This text changed
Existing Chinese translation创建项目Previous translation · Check needed
In your productWelcome backUnchanged
Existing Chinese translation欢迎回来
In your productInvite membersUnchanged
Existing Chinese translation邀请成员

The text changed. The previous translation stays available to compare and revise.

03 / FROM COMMUNITY TO YOUR OWN PROJECT

Enjoy the experience?
Bring it to your product.

Public ecosystems give you a place to start. When your own software, website, or content needs localization, organize translations and ongoing updates around a private team project.

  • Manage your own content

    Connect source content, translations, and versions in a dedicated project.

  • Work with the right people

    Organize collaboration around project visibility and member permissions.

  • Connect the next update

    Confirm the translation, review, and release flow supported by your adapter.

Talk about your project

Discuss your workflow and scope directly with the developer to arrange a demo.

Public ecosystems

Find supported tools and explore community localization.

Private team projectsIllustrative workspace · Sample data
Private project

Product website localization

Product interface / Source content

en-US→zh-CNja-JP
Versions & translationsV1 → V2
Project membersABC
Role-based collaboration

Your content · Dedicated projects · Ongoing maintenance

04 / BUILT FOR WORK THAT CONTINUES

Every contribution adds up.

Keep the work and its history.

Connect translations to their source and retain saved versions, giving your team a record to work from as content changes.

Refine the same expression.

Collaborate around the same source, with saved changes and explicit conflict feedback that keep the team's work traceable.

ABC
Conflict protection · Illustration

Different tools. A shared hub.

Ecosystem adapters handle content differences while the platform maintains translation and version relationships. Bring the results back where they are used.

05 / FROM SOURCE TO APPLICATION

Translations finish. Content keeps growing.

Connect each update to a shared workflow, with a clear source, version history, and publication record.

  1. 01

    Connect a source

    An ecosystem adapter identifies content locally and submits structured source information.

  2. 02

    Work together

    Collaborate around the same source, track saved versions, and resolve editing conflicts.

  3. 03

    Review and publish

    Confirm translations through the project workflow, keeping edits and published results distinct.

  4. 04

    Bring it back

    The corresponding client retrieves matching published translations and applies them in the ecosystem.

Integration and application vary by ecosystem. Confirm the flows available today when requesting access.

06 / BEFORE YOU START

A few things to know.

How do public ecosystems and private projects differ?

Public ecosystems help you discover and use published localization. Private team projects organize your own sources, translations, and workflow. Visibility and member access are managed for the project; discuss integration and service options in a demo.

Who is Trans-Hub for?

Developers, open-source maintainers, and translation teams maintaining multilingual content over time. You can also start with a specific ecosystem and explore or contribute to community localization.

How can I try it?

Explore the public ecosystems to see available sources and languages, or request access to discuss your workflow directly with the developer.

Can I connect any file or tool?

Integration depends on the corresponding ecosystem adapter. Check each ecosystem page and demo for current coverage. Additional formats and tools need separate validation.

LET YOUR WORK TRAVEL FURTHER

Good work deserves
a wider world.

Ready to localize your own product? Bring your team's content and workflow. Let's find the right approach for your private project.

Talk about your projectIndependently built. Open to early users and ecosystem contributors.