fix build instructions link

[bryevdv]

cc @ipdemes @manopapad not sure if we want ot try and re-deploy existing docs or now. The "build" page does exist, just the link from the "install" page was wrong.

[manopapad]

re-deploy existing docs

is that easy to do @ipdemes ?

[manopapad]

We should probably just set this up to happen automatically, instead of bothering someone to do it every time...

[ipdemes]

I will do it today (as soon as this PR is merged). But I agree that we probably want the process to be automatic in case I forget to update docs when needed.

[bryevdv]

Make what automatic, exactly?

If we deploy on every PR merge they would need to some dev/staging version for the next release. It would not make sense to update the previous docs automatically all the time, in case new features are in the latest branch that are not in the previous release. Or do you mean a GH action workflow_dispatch that can be manually kicked off when needed?

[manopapad]

I think a nightly/weekly/on-every-top-of-tree-commit automatic push would make sense. You're right that these "bleeding-edge" docs should be marked as such, and not override the docs from previous releases.

[ipdemes]

I agree with Manolis that we could automatically update documentation for current release periodically or per request. For example, if someone has labeled the PR as "documentation". So we could control when exactly this should happen. It would be also nice to be able automatically generate docs for the new release every time we create a new release branch.

[bryevdv]

I'm going to go ahead and merge :)