# How about i18n for ansible docsite? **URL:** \ **Category:** Ansible Project\ **Created:** [October 15, 2015, 2:10pm UTC](https://forum.ansible.com/t/how-about-i18n-for-ansible-docsite/19514 "2015-10-15T14:10:31Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![ADoyle](https://avatars.discourse-cdn.com/v4/letter/a/b9bd4f/32.png) [@ADoyle](https://forum.ansible.com/u/ADoyle)\ **Post date:** [October 15, 2015, 2:10pm UTC](https://forum.ansible.com/t/how-about-i18n-for-ansible-docsite/19514/1 "2015-10-15T14:10:31Z")
I’m willing to translate the docsite into chinese. But currently the .rst files are stored in the ansible repo with other code files. The repo is huge but the things I need are only in the docsite folder. Is it possible to separate a single project such as “ansible-doc” from the main repo for translation? ---
**Author:** ![James\_Cammarata](https://avatars.discourse-cdn.com/v4/letter/j/7c8e57/32.png) [@James\_Cammarata](https://forum.ansible.com/u/James_Cammarata)\ **Post date:** [October 27, 2015, 2:08pm UTC](https://forum.ansible.com/t/how-about-i18n-for-ansible-docsite/19514/2 "2015-10-27T14:08:18Z")
Hi! Thanks for the offer, however we're concerned about the logistics of scale required to maintain up-to-date translations of the docs, including all of the module documentation. It's something we've been discussing a lot recently, actually, and our main concern is the amount of time and dedication required to make sure the alternate language docs don't drift from the main docs. Due to the fact that our docs are kept with the source code, any PR to update the docs would have to be applied to all of the alternate languages. So, for now, if you'd like to begin working on this we'd recommend forking the repo (if you haven't already) and setting up an alternate directory for the translated docs, and we can look to use them in the future when we're ready for them. Thanks! James Cammarata Director, Ansible Core Engineering github: jimi-c