Translate doc to jupyter-book

[vPibernus]

Status : draft

This is a translation of the current doc, in a jupyter book format.
The translation is a work in progress, but fix the issues #120 and #121 .
The work do not include an update of the CI pipeline to compile the translated doc.

[jschueller]

-1
we moved away from ipynb examples because it had too much drawbacks: mainly versioning of binary data and difficulty to update/re-render the output cells

[SG-phimeca]

@jschueller: Note that jupyter-book is something different from jupyter notebook. jupyter-book can handle jupyter notebook sources. It also compiles markdown and plain.

Python.https://jupyterbook.org/en/stable/intro.html

[jschueller]

I still see .ipynb getting versionned here so I'm guessing jupyter-book still takes ipynb as source documents, which is bad for versioning
anyway imho its overkill to change tech just for badly sized images (their pixel sizes are just hardcoded)

[SG-phimeca]

Indeed. I think this is beacause the work is in an early stage. As mentioned by @vPibernus , “The work do not include an update of the CI pipeline to compile the translated doc.”.
Eventually, the shift would require to update the CI, and commit only the source.

The change in technology would fix some of the issues currently experienced.
I agree with the term overkill for just this.

The proposed technological change is motivated by the different syntax.
Current technology focus mainly on presenting python code.
Text is entered as commentaries.
Jupyter book seems more convenient (subjective opinion) for writing text.

All in all, I think this is a matter of personal taste.
Should we rewrite the doc (I think we should), the people involved will have to decide (again: opinion).