Pyro: multiple versions of documentation, one per release (+dev)

[dustinvtran]

Having docs for varying versions, especially dev and master, sounds useful for development. I don't know if Pytorch has a good solution but I like that TF has multiple versions. FWIW, read the docs does this automatically: https://docs.readthedocs.io/en/latest/index.html.

relevant: https://github.com/uber/pyro/pull/545#issuecomment-343333425

[ngoodman]

we did this in webppl (using readthedocs) and it worked nicely. (all though it meant i pointed people to the dev docs most of the time ;)

[jpchen]

unfortunately you can only do that if it is hosted on readthedocs.org. pytorch does this manually which is why they have this hacked together page. the problem with this is that, our doc files will scale with each release, which will be a lot of overhead when a user clones pyro.

[neerajprad]

How about hosting documentation / tutorials on readthedocs, and retaining our domain name - http://docs.readthedocs.io/en/latest/alternate_domains.html?

[jpchen]

oo hm this seems new ill look into this

[jpchen]

docs.pyro.ai (give 24 hours for CNAME to propagate)

[neerajprad]

Great!

• Can we opt out of the ads (http://docs.readthedocs.io/en/latest/ethical-advertising.html#opting-out)? They seem kind of pesky.
• Can we get our old CSS back?

[jpchen]

Can we opt out of the ads

nope - i already opted out of paid ads but thats all we can do on the free tier

Can we get our old CSS back?

Go for it :)