I’ve given these posts a new dedicated space in this topic instead of our announcement topic. Most points have been addressed by various other posts in this topic, and I will cover feature related points which have been missed out.
Just a quick note here – Google already translates our posts even before this feature was implemented. When a related query is searched for and unsupported, Google puts the forum through their proxy, e.g.
https://meta-discourse-org.translate.goog/t/content-localization-and-automatic-translations-for-your-community/370000?_x_tr_sl=en&_x_tr_tl=id&_x_tr_hl=id&_x_tr_pto=tc
(yes, that’s a legit search result on Indonesian Google. notice the domain)
However that’s very poor search experience and traffic through a proxy will not give you good data. This is one of the many reasons we’re building this feature.
Yes actually. It’s indicated in our documentation for this feature which was linked in the original OP.
I’ve spun out new topics from what I’ve gleaned here and I appreciate all the feedback 
There are some little quirks with regards to post language detection that I am aware of as seen in post 7 where it was detected as Czech instead of English, and other topics on meta.
Lastly folks, I’m going to request that we take time to think about what we’ve written here and how we’re all on the same page that we want the best for our communities. Wanting to understand each other’s culture is impressive, and I appreciate those who are trying.
There are a few things I am looking out for here (a new topic please)
- Is something consistently translated wrongly on meta?
- Are folks misunderstanding one another and is anyone uncomfortable?
- Is our interface clear over whether content is shown in the original language or translated?
Ultimately Discourse is a construction kit, so we would like to make sure we provide enough tools to set your multilingual community up for success.