anchor.diff:  stylesheet setup::
   The template scripts assume that the the css used to style the generated HTML is located under `<repo_root>/scripts/resources/css` and is called `giblish.css`. To enable a styling of your liking, either create this folder/css file in your repo at that exact place or tweak the `html_publish.sh` script to use another location/css file name for the styling.
   
  +other tweaking::
  +You can tweak the `publish_html.sh` script to use other features of giblish/asciidoctor, such as docid's, docinfo support and others. To do this, change the flags and arguments used to invoke giblish from the `publish_html.sh` script accordingly.
   
   == Deploy using Jenkins
   
  -This setup adds a Jenkins (or similar build orchestrator) installation so it is more to setup but is more 'production friendly'.
  -
  -
  -
  -
  -
  -
  -
  -
  -
  -
  -
  -
  -
  -
  -
  -
  -
  -
  +This setup adds a Jenkins (or similar build orchestrator) installation so it is more tools to setup but offer more flexibility and is probably more 'production friendly'.
   
   .Deploy using Jenkins
   image::deploy_with_jenkins.svg[]
  -
  -
  -
  -
  -
  -
  -
  -
  -
  -
  -
  -
  -
  -
  -
  -
  -== Toolchain
  -
  - * git
  - * giblish
  - * git server side hooks to kick-off the document rendering after a git push.
  - * a web server to publish the rendered html documents.
  -ö* a tool that can execute scripts after a git push. *Jenkins* is used in this instruction. Some advantages over calling giblish directly from a git hook:
  - ** the document rendering is asynchronous to the git push from the client.
  - ** the script executed by Jenkins (the 'pipeline' in Jenkis lingo) can be stored and versioned in the same git repo as the documents to be rendered.
   
   === Sequence for rendering documents
   
  
positive.code: = Setup web site powered by giblish
  :imagesdir: setup_server_assets
  :numbered:
  
  == Purpose
  
  To describe how to use giblish as a tool in creating a static web site with documents automatically generated from a git repo.
  
  This text covers two deployment scenarios; one using git hooks only, and one using a combination of git hooks and Jenkins. It has only been tested on Linux servers (Ubuntu). Most of the tools and scripts should work on a Windows server as well but might need some tweaking and is, again, not tested.
  
  == Deploy using git hooks only
  
  
negative.code: == Jenkins pipeline script
  
  Below is a very basic example of a Jenkins pipeline that triggers giblish to render html and pdf documents located in a specific directory in a git repository.
  
  TBD
  