Due to a combination of Gitlab changes, reducing maintenance overhead, and adopting best practices, all of the common-lisp.net/project sites have been moved to PROJECT-NAME.common-lisp.dev. So, ASDF's new website is https://asdf.common-lisp.dev. All of the old URLS are forwarded so existing bookmarks should continue to work.
I took a look at the new site and couldn't find any broken links with a quick glance (AFAIK, the only way to get a broken link in the move is if the href is an absolute path without hostname).
I believe next up on the "reducing maintenance overhead" TODO list is to move every site onto Gitlab pages (so no more shell access to common-lisp.net is needed to update a website). I don't know the timeline for that, but figured we should start planning for it now.
In order to move to pages, we need to create a repo asdf/asdf.common-lisp.dev and copy the current contents of the site into the public/ folder. Additionally, we need to add a very simple .gitlab-ci.yml file that has a
pages job in it. I believe Erik will do that for us if we ask (or take too long).
AFAICT, the current procedure for updating the website is to run
make website after a release. We'd need to change those jobs to instead copy the files into the new repo and push (instead of rsync).
I'd like to propose that at the same time (or instead of that) we add a new Gitlab CI job to this repo that handles all of that when a release tag is pushed. I've done a similar thing with cl-tar, so would be happy to set it up here as well. (I'm also likely going to write a News entry at some point for common-lisp.net that describes how to do it).