{"action":"closed","issue":{"url":"https://api.github.com/repos/rtfd/readthedocs.org/issues/3380","repository_url":"https://api.github.com/repos/rtfd/readthedocs.org","labels_url":"https://api.github.com/repos/rtfd/readthedocs.org/issues/3380/labels{/name}","comments_url":"https://api.github.com/repos/rtfd/readthedocs.org/issues/3380/comments","events_url":"https://api.github.com/repos/rtfd/readthedocs.org/issues/3380/events","html_url":"https://github.com/rtfd/readthedocs.org/issues/3380","id":280399878,"number":3380,"title":"mkdocs: where to specify mkdocs.yml - two translations of markdown documentation in one repository","user":{"login":"chfw","id":4280312,"avatar_url":"https://avatars0.githubusercontent.com/u/4280312?v=4","gravatar_id":"","url":"https://api.github.com/users/chfw","html_url":"https://github.com/chfw","followers_url":"https://api.github.com/users/chfw/followers","following_url":"https://api.github.com/users/chfw/following{/other_user}","gists_url":"https://api.github.com/users/chfw/gists{/gist_id}","starred_url":"https://api.github.com/users/chfw/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/chfw/subscriptions","organizations_url":"https://api.github.com/users/chfw/orgs","repos_url":"https://api.github.com/users/chfw/repos","events_url":"https://api.github.com/users/chfw/events{/privacy}","received_events_url":"https://api.github.com/users/chfw/received_events","type":"User","site_admin":false},"labels":[{"id":219122234,"url":"https://api.github.com/repos/rtfd/readthedocs.org/labels/Mkdocs","name":"Mkdocs","color":"009800","default":false}],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2017-12-08T07:36:22Z","updated_at":"2018-02-14T21:03:21Z","closed_at":"2018-02-14T21:03:21Z","author_association":"NONE","body":"## Details\r\n\r\nThere are multiple problems in this setup. I knew this is an edge use case. So firstly, we wondered if we can specify where mkdocs.yml is, like sphinx conf.py. And We got strange builds where build passed but no documentation accessible via the url.\r\n\r\n* Project URL: \r\nhttps://readthedocs.org/dashboard/pyecharts/\r\nhttps://readthedocs.org/dashboard/pyecharts-en/\r\n\r\n* Build URL (if applicable):\r\n\r\nhttps://readthedocs.org/projects/pyecharts-en/builds/6384125/ -> build passed but no pages there.\r\n\r\n* Read the Docs username (if applicable): \r\n\r\nchfw\r\n\r\n## Expected Result\r\n\r\nWe would like to build zh documentation in the master project and build en in pyecharts-en project.\r\n## Actual Result\r\n\r\n*A description of what actually happened*\r\n\r\nNo idea on how to tell readthedocs where mkdocs.yml is. Specifically, we would like the master project to use zh-mkdocs.yml and English project to use en-mkdocs.yml\r\n\r\nAnd in principle, is it supported to have two translsations of mark-down documentation in one repo?"}}
{"actor":{"display_login":"RichardLitt"}}