-
Notifications
You must be signed in to change notification settings - Fork 37
Description
A lot of links were broken with the migration to GitHub Pages because it doesn't support HTTP redirects. A solution based on Javascript on a 404 page was proposed by @huynhtrankhanh in #232 and it has allowed resolving the most pressing broken link issues. It can be extended to fix other broken links that need to be fixed.
We can live with this for a couple of weeks to see if we are satisfied with this solution, or if we prefer to migrate to an infrastructure that supports HTTP redirects, like @silene said he could explore.
I'm opening this issue to make the list of remaining things to fix after #232 (already fixed issues are #230, as well as the long-standing issues #196, #188, #131, #111, #110).
### Tasks
- [ ] #228
- [ ] Decide whether to ditch the HTML redirects under `pages/{distrib,stdlib,library}` for index and change pages.
- [ ] #231 (does this issue also apply to the 404.html redirects or would it be fixed by ditching the HTML redirects mentioned just above?)
- [x] Decide what to do with the https://github.com/coq/refman repository. Currently, it contains a copy of the documentation also present in the https://github.com/coq/doc repository under the current version. We could remove it and redirect to the current version of the refman just like it is done for the stdlib.
- [x] Possibly add the old versions of the documentation to the https://github.com/coq/doc repository so that their links are not broken either.
- [x] Revert or partially revert https://github.com/coq/coq/pull/18108.
- [x] List the remaining broken links based on what used to be in the Apache configuration files.
- [x] Add redirects for Nix links.
- [ ] Add redirects for coq-workshop links.
- [ ] Add redirects for tutorial links.
- [ ] Add redirects for opam links.
- [ ] Add redirect for related-tools.
- [x] Add redirects for wiki links.
- [x] Add redirects for Bugzilla links.
Regarding point 4 above, removing the https://github.com/coq/refman repository means that we would no longer provide a "moving target" refman version, and maybe that's a good thing (I was already suggesting this in #111). People could still craft "moving target" URLs based on our redirection mechanism. This would also make the release process simpler (one manual step to remove).