With Fastly we could probably send www.python.org/peps/ http://www.python.org/peps/ to RTD or docs.python.org/devguide/ http://docs.python.org/devguide/ to the devuide. I think RTD supports setting a canonical URL that includes a path too. FWIW. Of course the look and feel might be different so different domains might be a good idea anyways.
On Apr 11, 2017, at 12:50 PM, Brett Cannon email@example.com wrote:
With part of the goal of moving to GitHub being to minimize how much infrastructure we have to run, one of the long-term goals I have is to use Read the Docs to host Python's documentation. But to get there we have to move any "special" docs over first. That means relocating the devguide (it also means relocating the PEPs, but that's another issue and is blocked first and foremost by https://github.com/python/peps/issues/4 https://github.com/python/peps/issues/4).
Thanks to the work of various people we have https://cpython-devguide.readthedocs.io/ https://cpython-devguide.readthedocs.io/ so the toolchain for building the devguide on RTFD is done. That means the next step is deciding on a subdomain on the python.org http://python.org/ domain to host the docs from. If you have an opinion, go to https://github.com/python/core-workflow/issues/4 https://github.com/python/core-workflow/issues/4 and leave a reaction on the appropriate message. _______________________________________________ core-workflow mailing list firstname.lastname@example.org https://mail.python.org/mailman/listinfo/core-workflow This list is governed by the PSF Code of Conduct: https://www.python.org/psf/codeofconduct
— Donald Stufft