Automating Translations

[roblarsen]

Workflow?

1. Questions are edited in English
2. There are no translations in development or PR branches
3. development a new (soon to be) protected branch, is the target for PRs and ongoing development.
4. We create an Action for merges into main (monthly?) that
   1. Runs tranlsate.mjs (not the garbage version in this PR as of this writing, but a good version) which uses Azure translator api to translate to our target languages. We can add as many languages as we can translate for less than 2,000,000 characters a month.
   2. Creates a GitHub release (because why not)
   3. Build eleventy and pushes to gh-pages

Questions:

1. Still use eleventy and link to translations?
2. Would we want to copy the same multiple md file structure of the root for the translated folders?
3. What would we have to do to make sure we can still use eleventy on the automated translated markdown files.
4. Would it be better to serve the users preferred language?

[lgtm-com]

This pull request introduces 1 alert when merging d24a070 into 0a43c7a - view on LGTM.com

new alerts:

• 1 for Unused variable, import, function or class

[roblarsen]

@coliff (with an appropriate Azure translate API key) this code successfully reads markdown and writes a translated file. We can do 2,000,000 characters a month with the free tier or $10/1,000,000 characters for the pay as you go. The free tier should be fine as long as we aren't translating every file every time we do everything, so we just need to figure out a workflow where we call Azure appropriately alongside the site build process.

I think running an action on:release would make the most sense. That will definitely keep us under the limit, because we probably won't release all that often. If we do, we'll just have to deal with that going forward.

[lgtm-com]

This pull request introduces 2 alerts when merging 88e41ed into c62f285 - view on LGTM.com

new alerts:

• 2 for Unused variable, import, function or class

[roblarsen]

This code is complete, at least in terms of translating from Azure. 300,000 characters to translate the whole project.

There's plenty to-do here, but this is blocked by #743