anchor.diff:  
   To describe how to use giblish as a tool for creating a static web site with documents that are automatically generated each time a contributer push changes to a git repo.
   
  +If you want to dive straight in and setup one of the scenarios below, jump to <<setup_instructions>>, otherwise read on for some examples and considerations.
  +
   === Example usages
   
   TBD
  -
  -=== Some preliminary notes
  -
  -Permissions and security::
  -These instructions does not give any advice on setting up permissions in a way suitable for your use case. You should however, give this an appropriate amount of consideration. You need to set the permissions so that the relevant tools and scripts can perform their expected tasks without being security holes of your server. You might want to consider setting up specific user accounts/groups to achieve this but this is outside the scope of this text.
  -
  -Server side git hooks::
  -git supports hooks in several parts of the sequence of getting changes committed and pushed to a remote repo. This feature is used in both scenarios below to kick-start the HTML document generation when someone pushes a change to the git repository. For details on git hooks see https://git-scm.com/book/en/v2/Customizing-Git-Git-Hooks[this doc].
   
   == Two deployment scenarios
   
  
positive.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 (typically under /var/www/... )
  
  ==== Considerations when choosing this scenario
  
  Possible advantages::
   * it has few dependencies on external tools, only git, giblish and a web server are needed for this to work.
  
negative.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
  
  