anchor.diff:  the `my_dst_root` dir.
   ====
   
  -.Advanced usage; Publish a static html site from a git repo
  +.Advanced usage; Publish a static html site from a git repo with search capabilities
   ====
   giblish can be used to inject a tree of html docs suitable for serving via a web
   server (e.g. Apache). Below is an example how to create such a tree. If you
   combine this with a server side git hook that invokes this script after push,
   you will have a way of auto publish your latest documents and/or documents at
  -specific git tags. In principle a poor-mans document managing system.
  +specific git tags. A document management system including nice index pages and
  +text search capabilities
   
   Assumptions:
   
  
positive.code:  * You want to publish the documentation as it looked for your release tags
     myprod-v1.0-final, myprod-v2.0-final, ...
  
   giblish -t "-final$" -r ~/gh/myrepo/common/resources -s mylayout -w /var/www/html ~/gh/myrepo/common/Documents /var/www/html/proddocs
  
  The above will create a tree of html docs under `/var/www/html/proddocs`. Each
  tag will get its own subdir (e.g. `/var/www/html/proddocs/myprod_v1.0_final`).
  
negative.code: 
  giblish is used to convert a source directory tree containing AsciiDoc files to
  a destination directory tree containing the corresponding html or pdf files
  and add some handy tools for easier navigation of the resulting files.
  
  The tools include:
  
   * An index page listing all rendered documents with clickable links
   * Document ids - Note: the implementation of this is giblish-specific and thus
     you need to render your adoc files using giblish to make this work as intended.
     You can use document ids to:
   ** Reference one doc in the source tree from another doc without depending on file
      names or relative paths. The referenced doc can thus be moved within the sourc
      tree or change its file name and the reference will still be valid.
   ** Validate doc id references during document rendering and thus be alerted to
      any invalid doc id references.
   ** Let giblish generate a clickable graph of all document references (requires
      graphviz and the 'dot' tool).
   * A (stripped-down but nonetheless useful) text-search of your documents (requires
     that you view your docs via a web-server.
   * If the source directory tree is part of a git repository, giblish can generate
     separate html/pdf trees for branches and/or tags that match a user specified
     regexp (see examples below).
  
  == Dependencies and credits
  
  Giblish uses the awesome *asciidoctor* and *asciidoctor-pdf* projects under the hood.
  Thank you @mojavelinux and others for making these brilliant tools available!!
  
  == Installation
  
  