Build docs for current release instead of for `develop` branch?

[amoodie]

Currently we build docs from the develop branch, which sometimes (often) is ahead of the latest release. I think the docs should reflect the most recent release.

@mcflugen I know you wanted to migrate to another docs platform (readthedocs?). Is this a good time do that and have mutliple docs versions?

If it's not a good time to do that, maybe we should change to building docs from a branch release and only merge there once we are ready to release a new version? Or have version branches and only merge those into main when we are ready to release (renaming develop to main)?

[amoodie]

@mcflugen do you have any thoughts on this? Would be good to be able to have different versions of docs (or at least a develop and latest release), especially as we gear up to break things with upcoming releases.

[mcflugen]

@amoodie I agree. readthedocs is good for hosting different versions of the docs so that sounds like something worth doing. I'll have a look to see how difficult it might be. One issue is that sandpiper.readthedocs.io is already taken; sandplover.readthedocs.io isn't, though, which is probably what we want anyway.