docs: Migrate docs to new build#7119
Conversation
christopher-hakkaart
commented
May 8, 2026
- Squashed from dev branch to help with noise
Signed-off-by: Christopher Hakkaart <[email protected]>
4b411d7 to
197e932
Compare
Signed-off-by: Christopher Hakkaart <[email protected]>
Signed-off-by: Christopher Hakkaart <[email protected]>
Signed-off-by: Christopher Hakkaart <[email protected]>
✅ Deploy Preview for nextflow-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
7e9c8c2 to
f2077f2
Compare
Signed-off-by: Phil Ewels <[email protected]>
Signed-off-by: Phil Ewels <[email protected]>
Signed-off-by: Phil Ewels <[email protected]>
Signed-off-by: Phil Ewels <[email protected]>
b506e15 to
0587abd
Compare
Signed-off-by: Phil Ewels <[email protected]>
f8457f3 to
4c33ce6
Compare
|
@bentsherman @pditommaso this PR is now good to merge. docs.seqera.io/nextflow is currently on a Netlify property that @christopher-hakkaart pushes manually, so nothing will happen immediately on merge. Once we have checked that the new production build at https://nextflow-docs.netlify.app/ looks good (404 until this PR is merged) then we will update the redirect and the docs will go back to being automatically updated again. Deployment previews for docs changes on PRs will be valid and updated again, and we should pay attention to any docs build failures that get reported (if PRs are merged with docs CI failures then there's a good chance that it could stop new builds for all projects on docs.seqera.io). We've done pretty extensive testing on this PR now and are happy that it's stable and good to merge. Hopefully in the near-ish future we will have a fairly major docs rearchitecture project go through, at which point we can return and delete the |