Make the projects work with multiple languages and locales

[Greenheart]

We already have support for translations in the idg.tools project, and in the cms.

But we need to make some tweaks before we can start using it properly.

• Here's an interesting solution that might give us a better development experience than the standard i18n solutions: https://github.com/ivanhofer/typesafe-i18n
• We could use the CMS to allow people to edit translation strings and add new content.
• Potentially we could create tooling to keep track of when translations have changed in one language, and prompt the team to validate the same content in other languages - or add it if it's missing. But this is a future idea.

• [ ] One first step is to add this as a way to contribute on https://IDG.community/contribute. There's already a draft text that could be edited and published in the content for that page.
• [ ] Another step is to create a room for translations of the IDG Toolkit and community content. Then invite people who want to get involved in translations to join that room and organize.
• [ ] Also highlight the need for help with translations on the roadmap entry on IDG.tools
• [ ] Make use of machine translation APIs to get a rough draft for languages that we can't yet manually translate. Then add a disclaimer and encourage people to help us keep translations up to date.

---

Update 2023-01-19 - integrating with a localization solution

Weblate seems like a good option, and it integrates with Git so that we can use both machine translation as well as human translations, and best of all sync it between the CMS as well as the Weblate project. This means translators will be able to use a powerful tool for their needs, while content creators can work with the CMS. And developers and designers can work with Git like usual.

https://docs.weblate.org/en/latest/vcs.html