Automatic code doc generation

[sphamba]

Prework

• I understand and agree to this repository's code of conduct.
• I understand and agree to this repository's contributing guidelines.
• I have already submitted an issue or discussion thread to discuss my idea with the maintainers.

What kind of change does this PR introduce? (check at least one)

• Bugfix
• Feature
• Code style update
• Refactor
• Build-related changes
• Other, please describe: documentation

Does this PR introduce a breaking change? (check one)

• Yes
• No

If yes, please describe the impact and communicate accordingly:

The PR fulfills these requirements:

• It's submitted to the branch named as follow :
  • Add a reader: reader-<institute>-<campaign>
  • Fix a bug: bugfix-<some_key>-<word>
  • Improve the doc: doc-<some_key>-<word>
  • Add a new feature: feature-<some_key>-<word>
  • Refactor some code: refactor-<some_key>-<word>
  • Optimize some code: optimize-<some_key>-<word>
• When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)
• Don't forget to link PR to issue if you are solving one.
• All tests are passing.
• New/updated tests are included

If adding a new feature, the PR's description includes:

• A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

Related GitHub issues and pull requests

• Ref: #

Summary

• Automatic documentation of code using make
• Changed template to Sphinx book

[ghiggi]

Thanks a lot !