Still to do:

- check that everything has been moved
- possibly: links on GitHub release overview point to wiki. Handle this somehow.
- make wiki read-only for retirement
- create versions for last few releases
- let www.fast-downward.org point to the new website
- retire old auto-doc script in misc/autodoc/

I updated the release workflow instructions:

https://github.com/aibasel/downward-markdown/commit/066ec93373e4d7840974e4128c36accf1295e3d3 (change set)
https://new.fast-downward.org/latest/for-developers/release-workflow/ (result)

Can we also make updating the release instructions page part of this?

I understand that making a new release requires doing something to make them appear on the website and to update "latest", right?

We did most of the transition during the sprint. The code-specific documentation now lives in the main code repository, the other part of the wiki was moved into a new repository aibasel/downward-markup. The new website is hosted on github pages, via a new repository aibasel/downward-website.

Theoretically, automated website updates on all changes have been in place, but the involved GitHub Actions have not been stress-tested, yet. There are also a few small other things left to do before we can close this. I added them in the Optional Summary.

We would like to move parts of the documentation to the main repository, so that we can still access the documentation for older releases. This will include a major revision of the main website, abandoning the old wiki.