Devs write i18n migrations

All changes to translation files (adding terms, updating terms, removing terms, ...) happen using migrations. These migrations can be played on a dev's local machine or on the CrowdTranslate server. They can also be rolled back.

Google Translate means no waiting

When a migration is played, we use Google Translate to get a "good enough" translation.

Translators edit terms on CrowdTranslate

Translators are always just one version behind. Once changes have been pushed to CrowdTranslate, they can work on correcting any mistakes that Google Translate made.

CrowdTranslate syncs with prod

This means you don't push to CrowdTranslate, unless and until you are also pushing to prod. Until then, you just run any migrations you have against the most recent translations.

No merge conflicts

Your migration files lives in git. Your i18n files get downloaded when you need them.

---

If you have other questions not covered here, please email jeremy.lightsmith@gmail.com

Our approach has been inspired by Fowler and all the others that began using migrations for databases. Thank you.