Ralf D. Müller

hm. that is a thought one. If we use the dev-version of docToolchain for the production docs, we could easily break the prod docs, couldn't we? But you are right,...

ok. protected ng branch and always review of the generated content fits

@jmini when I take a look at the deployment script (http://doctoolchain.org/docToolchain/v2.0.x/025_development/030_create_new_release.html) I think with a proper deployment created, the versions will be correct. the problem last time was, that I...

as long, as the visible content on the doctoolchain website is ok, I think it is not a big problem if it renders with a slightly older version. And you...

btw: one solution would be to set the doctoolchain version configured in dtcw to `latest`. But this is now also the master dtcw file which is used in the install...

here is some code for image manipulation: https://github.com/asciidoctor/asciidoctorj-screenshot/blob/7991c455c5079ceba1d8b097f0dbe8904df9c248/src/main/groovy/org/asciidoctor/extension/ScreenshotTaker.groovy

can you share your modifications? You mentioned CROWD in the issue description - dies you modification has to do with the authentication?

yes, but afaik does the confluencePublisher not use cookies. but I guess the exception is because of the crows cooky. we have the same problem with docToolchain ..

hm. So, we would have to replace the `rightcolumn.gsp` with something like this: ``` ``` and define in the config something like this: ``` gitRepoEditUrl = { sourceFileName -> return...

yes, if we change it in the default theme, this will break things. but we can check if the url is a String or a Closure: short form: ``` ```...