Multilingual: let's talking about translation strategies

[ramon-bernardo]

Zola now has basic support for multiple languages, let's talking about translation strategies.

See Zola example.

[alice-i-cecile]

So, we've got a few areas we could target with translation:

1. Home page: reasonably high priority, this is the top of our funnel
2. Bevy Marketplace: helps the user experience, and eventually core to revenue. Descriptions for each plugin or asset would be hard though.
3. Book: very unstable still, but very important for learning.
4. Release notes: helpful to translate, but not useful until we have a sizable population of devs in that language who aren't comfortable with the English version
5. Migration guides: as above, but perhaps less important, as these tend to be quite mechanical and technical
6. Assorted news posts: low priority, these are nice, but not critical content

[cart]

As a note: before undertaking translation efforts we should sort out a way to track translation progress and track "drift" when we make a change to the english "source". If we can't have a trustable view of the state of things, we risk having "wrong" documentation / website info in other languages, which is actively harmful. And considering that people will already have trouble finding non-english support (because english is where most of our "help" threads and github discussions happen), "wrong" docs are very dangerous / could waste a lot of time.

Additionally, given that Bevy docs / website content is still very "in flux", I think we should keep this hyper-scoped until things settle down (probably just translating the front page + general navigation).