[FEATURE] Using Markdown for the online doc

[lmichel]

Is your feature request related to a problem? Please describe.

Both issues #90 and #75 mention a doc folder for documentation resources.

These doc files could be in HTML, but HTML is painful to update (never updated thus)

A convenient solution would be to use Markdown for these resources. This allows good rendering with an easy edition.

There are many JS tools able to process MD resources.

We have to select one and use it everywhere we have to display static online documentation.

[galyfray]

tooltips and other things could be handy to put in those docs. we could use the java's file formats for location making it easier to change or correct any message as a lot of message are hidden somewhere in the code and are kind of a pain to find when information is missing or there is a typo in it ...

[lmichel]

Great, but according to the time left, I suggest to keep focused on the main features

[lmichel]

We have to separate the label management and the online docs:

• Label: one JSON file like {LABEL: text...} loaded at startup and accessible as a global variable for the whole application. The can be made in a progressive way, label per label.
• Doc: the doc text, e.g. credit, are longer and more structured the simple labels. they must be store in individuel MD pages. The HTML conversion could be made by a specific JS module.

[lmichel]

This issue is related to #90 #110