I’ve started using Documenter.jl to build up documentation for a (non-public) package I maintain. Because of the somewhat limited tools available to me and my team, I think I’ve come to the conclusion that the best way to allow users to access the docs is to keep them in the repository itself as markdown files (similar to what HDF5.jl does does.
I’m trying to figure out the best workflow for keeping the docs up to date, though. I have CI set up on our local Gitlab server for testing, and it would be nice to have that process also build/update the docs, but if the resulting markdown files are to be kept in the repo itself, I’m not sure there’s a way to do it that way.
Am I limited to just manually building the docs each time they’re updated and committing the new markdown files to the repository? Or is there a better way?