It would be nice to have that here too! Right now any authorized CI run will overwrite the main content of the page.
One option I was thinking of was to use quarto render instead of quarto build, and use Documenter.jl's deploydocs system to create directories in gh-pages where builds off of different places deploy to different paths:
main deploys to dev,
tags deploy to version number prefixes,
the latest tag is linked to stable, and
PRs deploy to previews/PR$pr_num.
This is a notable departure from the regular geocompx deployment method, is this something we should add?
In Julia documentation we have the ability to push "preview" builds of PRs, that don't replace the main docs, but are in a subfolder in the gh-pages branch like
/previews/PR$pr_num
. See e.g. https://juliageo.org/GeometryOps.jl/previews/PR206/ vs https://juliageo.org/GeometryOps.jl/stable for an example.It would be nice to have that here too! Right now any authorized CI run will overwrite the main content of the page.
One option I was thinking of was to use
quarto render
instead ofquarto build
, and use Documenter.jl's deploydocs system to create directories ingh-pages
where builds off of different places deploy to different paths:main
deploys todev
,stable
, andpreviews/PR$pr_num
.This is a notable departure from the regular geocompx deployment method, is this something we should add?