Explore our crowdin integration options

[bmuenzenmeyer]

The GitHub sync process - visible at #7089 is nice but has led to maintainer noise and some manual interventions.

This ticket should explore the use of:

• https://store.crowdin.com/github-action | Github with lots of config
• https://store.crowdin.com/in-context (Crowdin In-Context doesn't sync content, it allows to submit translations directly on the side)

From Andriy

Translations made via In-Context will be saved to your Crowdin project and then synced back to GitHub via connector or GitHub Action

Using both might create the best experience.

demo at https://demo.crowdin.com/

I want to make sure any live integration doesn't impact site performance or security.

[AugustinMauroy]

Can we can just to a script that we trigger with a cron job, that create a commit with all transition ?

[bmuenzenmeyer]

I dont like a custom approach - I'd rather use vetted, version-controlled tools. The GH Action has a lot of configurability and the support of Crowdin. A custom cron would eventually resemble the action, I suspect.

[dies]

Integration via Github Action is definitely a great idea! It's a recommended way to integrate Crowdin with Github. By the way, you can reuse your crowdin.yml. Please let us know if we can help you with the transition.

As for in-context, this technology is really useful for translating product copy, such as UI menu items and button titles, which are super hard to translate without context. Since you're translating MDX, each page itself carries enough context, they're perfectly fine to get good quality translations when translated in Crowdin.

[ovflowd]

@bmuenzenmeyer, how are we doing with the GitHub Actions implementation? Did you get any time to start a draft here?

[bmuenzenmeyer]

I started it and then got distracted by collab summit / travel and not having 1password access at the time.

I can try to land a draft soon.