anchor.diff:  That's it. You can now push to your _Main Repo_ and the `post-receive` hook will run `giblish` on the branches that you set it up to.
   
   === Setup the git hook and Jenkins scenario
  -
  -TBD...
   
   First, follow the steps described in <<common_setup>>. Then proceed with the steps below.
   
  
positive.code: The common (bare) git repo used by all content writers to push updates to. This repo shall be setup with a server-side hook (_post-receive_) that initiates the html generation and is triggered by each push to the repo.
  
  A 'Staging Repo'::
  A mirror of the _Main Repo_ that fulfills two functions:
  
   . to provide a checked-out working tree with the source files (adoc files).
   . to provide a script that uses giblish to generate html documents and publish those docs to a location where a 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 (e.g under /var/www/... )
  
  === Pros & Cons
  
  
negative.code: +
  NOTE: If you start with an empty, bare, _Main 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 _Main 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.
  
  === Scenario 1 - use a git hook and shell script
  
  First, follow the steps described in <<common_setup>>. Then proceed with the steps below.
  
  