Open ramon-bernardo opened 2 years ago
So, we've got a few areas we could target with translation:
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).
Zola now has basic support for multiple languages, let's talking about translation strategies.
See Zola example.