anchor.diff:  Adding an image title is mandatory to avoid empty broken spaces in the content.
   If necessary, you can add more parameters separated by a comma between the same brackets as the image title, such as the desired width, height, etc.
   
  -NOTE: use values in % for image size. For example; `\image:landscape.png[Landscape,70%]`
  +NOTE: Use values in % for image size. For example; `\image:landscape.png[Landscape,70%]`
   
   === Tables
   
  -In a general manner, avoid using tables if there are other solutions available. This is especially the case for complex tables that include assets or big code samples can lead to display issues.
  +In a general manner, avoid using tables if there are other solutions available. This is especially the case for complex tables that include assets or big code samples, as these can lead to display issues.
   
   .Table example
   [role="table-striped table-hover table-ordered",options="header,autowidth"]
  
positive.code: 
  === Admonition blocks
  
  The following elements can be used. However, avoid using them one after another as it can make reading more difficult:
  
  - `NOTE:` for a simple information note
  - `IMPORTANT:` for a warning. Warnings should include information that lead to important errors if not taken into account
  
negative.code: 
  For general guidelines about Asciidoctor, refer to the https://asciidoctor.org/docs/asciidoc-syntax-quick-reference[Asciidoc Syntax quick reference] page.
  
  == How to contribute
  
  There are two ways to suggest modifications or new content. Both of the options below require you to have a GitHub account created.
  
  * On every page of the *Talend Component Kit* Developer Guide, a *Suggest and edit* button is available. It allows you to access the corresponding source file on GitHub and to create a pull request with the suggested edits. The pull request is then assessed by the team in charge of the project.
  
  * Fork the https://github.com/talend/component-runtime[Runtime] repository of the *Talend Component Kit* project and edit .adoc files located under `documentation\src\main\antora\modules\ROOT\pages`. Make sure to follow the guidelines outlined in the current document, especially for large modifications or new content, to make sure it can properly be rendered. When done, create a pull request that will be assessed by the team in charge of the project.
  
  == General organization guidelines
  
  The documentation is made of:
  
  - Documentation files manually written under `documentation\src\main\antora\modules\ROOT\pages`.
  - Documentation files automatically generated from the source code under `documentation\src\main\antora\modules\ROOT\pages\_partials`. These files are individually called in manually written files through includes.
  - Assets, especially images, stored in the `documentation\src\main\antora\modules\ROOT\assets` folder. Some subfolders exist to categorize the assets.
  
  Each file has a unique name and is rendered as a unique HTML page.
  Some of the files are prefixed to help identifying the type of content it contains. Most common examples are:
  
  - `index-` for pages referenced from the main index page. These pages also contain specific attributes to be correctly rendered on the main index page (see 'List of metadata attributes' below).
  - `tutorial-` for tutorials/guided examples.
  - `generated_` for pages generated from the source code. These pages are generally stored in the `_partials` folder.
  
  == List of metadata attributes
  
  