i18n support and its community

**Is your feature request related to a problem? Please describe.**

Users in the world have a very different level of English experience and therefore many major OSS communities have i18n docs repositories or a system where people can contribute to translation as a bridge to help people to access to the necessary information and learn. In fact, almost all users in the last Amplify Meetup#1 in Japan seem to need translated documentation and I'm writing this proposal to have the i18n system and its community by combining the translation culture in OSS and users' voices.

**Describe the solution you'd like**

In my understanding, there are three major ways and my recommendation follows the order:

a. Open separate org for docs and welcome translation contributors to the org as a champion of each languages. Then community activities can be lead by the communities. It'll be something like `amplify-community` org. e.g. -
+ React.js community https://github.com/reactjs/ja.reactjs.org

b. Make a separate repository for i18n and have some owners who can maintain the WG and translated documentations. It'll be something like `ja.amplify.aws` repository. e.g. -
+ Vue.js https://github.com/vuejs/jp.vuejs.org
+ Angular https://github.com/angular/angular-ja

c. Integrate a service like [crowdin](https://crowdin.com/) for i18n and have some owners who can maintain the WG and translated documentations.
+ Node.js https://github.com/nodejs/nodejs.org/tree/master/locale
+ WG https://github.com/nodejs/nodejs-ja

**Describe alternatives you've considered**

As fas as I heard from community leaders from some of the above communities in Japan, they feel welcomed and more motivated when they are invited to the org as a collaborator and help people by translating as a team. I think it's not simple for Amplify as it's OSS and AWS's product at the same time so that translating by collaborating with AWS's professional translators might be an alternative.

**Additional context**

One more thing to add here is that there is no practical machine translation system yet and that's why i18n WG exists in many communities. In addition, I'm sure this situation is not only within Japan, but please forgive me to mention examples around Japanese communities where I live and know well. I'm happy to hear more voices from users in different regions.