anchor.diff:  
   === Setup the git hook and Jenkins scenario
   
  +First, follow the steps described in <<common_setup>>. Then proceed with the steps below.
  +
   TBD
  +
  +==== Sequence for generating documents
  +
  +The following image shows how the sequence from user commit to generated documents.
  +
  +.Sequence diagram for generating docs from adoc
  +image::Render Documents.png[]
   
   [appendix]
   == Scripts
  
positive.code:  .. Copy a bare repo you already use to the _Server_ file system.
   .. Init a new repo using `git init --bare <your_repo_name>` somewhere on the _Server_ file system.
  +
  NOTE: If you start with an empty, bare _Master Repo_ on the _Server_, it is a good idea to directly clone it to your local machine, commit some content to the 'master' branch and push the result back to the _Master Repo_. An empty, bare repo does not even contain a 'master' branch from the start and this can lead to some edge cases that complicate things.
  
  === Setup the git hook and shell script scenario
  
  
negative.code:  . provide a script that uses giblish to publish the adoc files in the working tree as HTML files that reside at a place in the file system where the web server can access them.
  
  Web Server::
  Apache, Ngnix or other web server that provides clients with HTML pages located somewhere on the file system on the server (eg under /var/www/... )
  
  ==== Considerations
  
  Possible advantages::
   * it has few dependencies on external tools, only git, giblish and a web server are needed for this to work.
  