I'm in the process of migrating all of my documentation off of readthedocs. While the projects I have which used their own subdomain don't have this issue, for projects served off of .readthedocs.io, there's no capability to issue a global redirect to the new host. While hacky approaches like uploading a sphinx build with a JS redirect might work, this is really not worth my time. While I see that there are some limitations with redirects as per #1916, this is really just at the top level host entirely, and can be an alternative to the "404" page.
Or even, if it were just possible for the 404 page itself to print the HTML, "project X has moved to Y", that would be enough. As it stands, I'm going to have some frustrated users not finding my new docs for awhile (when they come to me, I'll point them to this issue :) ).
I'm in the process of migrating all of my documentation off of readthedocs. While the projects I have which used their own subdomain don't have this issue, for projects served off of .readthedocs.io, there's no capability to issue a global redirect to the new host. While hacky approaches like uploading a sphinx build with a JS redirect might work, this is really not worth my time. While I see that there are some limitations with redirects as per #1916, this is really just at the top level host entirely, and can be an alternative to the "404" page.
Or even, if it were just possible for the 404 page itself to print the HTML, "project X has moved to Y", that would be enough. As it stands, I'm going to have some frustrated users not finding my new docs for awhile (when they come to me, I'll point them to this issue :) ).