Morten Piibeleht

By the way, I noticed that the [last CI for the nightly PDF crashed](https://github.com/JuliaLang/docs.julialang.org/actions/runs/2217265597). It's probably due to this escaping issue?

I'd say that Documenter is already designed to push to the `gh-pages` of the same repository. This is what all the packages I've seen do and what Documenter's manual recommends....

Added two things related to the automatic deployment on Travis: - Be explicit about why deployment is getting skipped -- saying "Skipping deployment" is not very helpful to the user...

> @mortenpi I'm running into this right now. Gadfly's docs are skipping deployment and I'm not sure why: https://travis-ci.org/GiovineItalia/Gadfly.jl/jobs/204402798 You're missing the `DOCUMENTER_KEY` variable, which is the only authentication method...

@felixcremer I agree that it is in some ways suboptimal, but it is consistent with how the argument was handled before -- if it didn't agree with `TRAVIS_JULIA_VERSION`, it would...

> I think it would be good to error out or exit with a non-zero exit code if the should_deploy variable is false. `deploydocs` shouldn't error simply when it decides...

> I'm a bit confused about makedocs, why doesn't it do the versioning etc.? One answer would be that `makedocs` generally just produces a bunch of files for a _single_...

They are created by `deploydocs` when `build/` gets copied over: https://github.com/JuliaDocs/Documenter.jl/blob/68dbd53d4ff6b339e795a4a3328955ad5c689e0e/src/Documenter.jl#L609 (with [`gitrm_copy` defined here](https://github.com/JuliaDocs/Documenter.jl/blob/68dbd53d4ff6b339e795a4a3328955ad5c689e0e/src/Documenter.jl#L754-L781))

@manuelbb-upb: are you still interested on working on this? I agree with @fredrikekre's feedback, but I would go further and say that I am not sure that the whole unique...

I think the best way to contribute here would be to create a simple prototype that runs the Julia manual on Stork, to see if and by how much it...