anchor.diff:  Notable things included in the website are out of the QiWeb releases lifecycle, like Skeletons and Samples.
   Thus, this is built in a separate project, in a separate git repository named `qiweb-website`.
   
  +
  +== Contributing to Documentation
  +
  +The documents can use code snippets which will extract code from the project.
  +This is preferred way to include source code in the documentation, since any refactoring will be reflected in the
  +documentation.
  +
  +Try to put one sentence on each line.
  +Lines without empty lines between them still belongs to the same paragraph.
  +This makes it easy to move content around, and also easy to spot (too) long sentences.
  +
  +As `{}` are used for Asciidoc attributes, everything inside will be treated as an attribute.
  +What you have to do is to escape the opening brace: `\{`.
  +If you don’t, the braces and the text inside them will be removed without any warning being issued!
  +
  +
  +== Document your modules
  +
  
positive.code: Documentation website is then generated from an aggregated JBake project.
  The result is assembled in a ZIP archive published with the `doc` classifier for easy download and offline browsing.
  
  
  === Website
  
  The QiWeb website provide general information about QiWeb and its community and embedd documentation sites for all past,
  current and develop versions documentations mini-sites.
  
negative.code: All documentation source is assembled in a ZIP artifact published with the `doc` classifier.
  
  
  === Documentation targets
  
  [discrete]
  ==== Development shell
  
  The `org.qiweb:org.qiweb:doc` project host the `DocumentationPlugin` that gets automatically registered in development
  mode and setup routes to serve documentation at `/@doc`.
  