Localization strategy?

[mikeal]

We need to figure out how community members can contribute localizations to the lessons.

[lidel]

@mikeal we should add it to https://www.transifex.com/ipfs/public/ :)

Steps I see:

1. Create a PR which moves English strings to separate source files, preferably in JSON-ICU format (to make it framework-agnostic and integrate with Transifex without conversion step).
   Some prior art:
   • In new WebUI we're using i18next with i18next-icu, the setup is quite straightforward.
   • There is an open PR adding i18n to IPLD Explorer that you can check as well: feat: add i18n support ipfs/ipld-explorer-components#1
   • Those apps use React, but i18next bits will be mostly the same. I see there is also a helper for Vue: @panter/vue-i18next, but I had no experience with it.
2. In the same PR add .tx/config and create a project at Transifex (ping @lidel)
3. Merge to master
4. Set up Transifex to automatically check source strings from master for updates

Step 1 is a chore but If you create PR with that, I can set up the rest :)

For more info about Transifex part, see References in ipfs/ipfs-gui#50

[terichadbourne]

Closing in favor of #268 which I created accidentally as a duplicate. Have moved the detailed notes over there for reference.