anchor.diff:  
   Possible advantages::
    * it has few dependencies on external tools, only git, giblish and a web server are needed for this to work.
  - * giblish provides templates for both the `post-receive` hook and the `publish_html` script that can be tailored to your specific setup quite easily.
  + * giblish provides templates for the `post-receive` hook.
   
   Possible drawbacks::
    * The hook and publish scripts provided with giblish runs syncronously at each push from a _Doc Writer_ to the _Master Repo_. The time it takes to generate the HTML docs from the adoc source will thus be added to each push to the _Master Repo_.
    * You need to manually setup the _Staging Repo_ on the server and this is a bit more 'hackish' than letting a build orchestrator tool implement a proper 'build' of your documents. You might for example end up with race conditions if two pushes to the _Master Repo_ are done close in time.
  - * The `publish_html` script provided with giblish only uses the currently checked-out branch on the _Staging Repo_ (typically 'master') to generate the HTML docs. It is non-trivial to add multiple-branch generation to the provided script.
   
   === Using Jenkins / git hook combo
   
  
positive.code: image::Render Documents.png[]
  
  [appendix]
  == Scripts
  
  .The giblish `publish_html.sh` template script
  [%collapsible]
  ====
  [source,bash]
  ----
  include::../scripts/publish_html.sh[]
  ----
  ====
  
  .The giblish `post-receive` template git hook
  [%collapsible]
  
negative.code: First, follow the steps described in <<common_setup>>. Then proceed with the steps below.
  
  script setup::
   . Find out where the template scripts for the `post-receive` hook by running `gem which giblish`. Strip of the `lib/giblish.rb` from the end of the returned path and `cd` to the resulting folder. There should be a subfolder named `scripts` under which you can find the template scripts somewhere.
  +
  .Installation on Ubuntu 16.04
  ====
  