Add Sphinx project documentation

[Aurelien7777]

Modifications

• ajout de la documentation Sphinx ;
• ajout du thème Read the Docs ;
• documentation de l'installation et du démarrage rapide ;
• documentation de l'architecture et des modèles ;
• documentation des interfaces et cas d'utilisation ;
• documentation du déploiement Docker, GitHub Actions et Render ;
• documentation de la surveillance avec Sentry ;
• ajout de la configuration .readthedocs.yaml.

Vérification

• génération locale réussie avec .\make.bat html ;
• aucune erreur ni aucun avertissement Sphinx.

Summary by Sourcery

Add a Sphinx-based documentation site and hosting configuration for the project.

Build:

• Add Sphinx makefiles and Windows batch script to build the documentation locally.
• Configure Read the Docs build via .readthedocs.yaml and a docs-specific Python requirements file.

Documentation:

• Introduce a Sphinx documentation project with Read the Docs theme and French-language configuration.
• Add structured documentation sections for installation, quickstart, architecture, database, interfaces, technologies, usage, deployment, monitoring, and project presentation.

[sourcery-ai]

Reviewer's Guide

Adds a full Sphinx documentation scaffold (with Read the Docs theme) for the project, including build tooling, configuration for Read the Docs, Python doc requirements, and initial documentation structure with placeholder .rst files for key topics.

File-Level Changes

Change	Details	Files
Introduce Sphinx documentation project with HTML build tooling for local development.	Add Windows make script to drive Sphinx builds via sphinx-build with a help target and argument handling. Add Unix Makefile to invoke sphinx-build in make-mode for all standard Sphinx targets. Configure Sphinx project metadata (project name, author, version, language) and basic HTML options such as the Read the Docs theme and static/template paths.	docs/make.bat docs/Makefile docs/source/conf.py
Configure Read the Docs and documentation-specific Python dependencies.	Add Read the Docs configuration file targeting the Sphinx config under docs/source/conf.py and failing the build on warnings. Pin Sphinx and sphinx-rtd-theme versions in a dedicated docs/requirements.txt used by Read the Docs.	.readthedocs.yaml docs/requirements.txt
Create initial documentation structure covering installation, architecture, usage, deployment, and monitoring.	Add top-level index and presentation/quickstart/usage documentation entry points as separate .rst files. Add topic-specific .rst placeholders for architecture, database, interfaces, technologies, deployment, and monitoring documents. Prepare Sphinx source tree layout (source directory with multiple .rst pages) ready to be wired into the toctree in index.rst.	docs/source/index.rst docs/source/presentation.rst docs/source/quickstart.rst docs/source/usage.rst docs/source/installation.rst docs/source/architecture.rst docs/source/database.rst docs/source/interfaces.rst docs/source/technologies.rst docs/source/deployment.rst docs/source/monitoring.rst

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've found 2 issues, and left some high level feedback:

• Consider adding the Sphinx build output directory (e.g. docs/build/) to .gitignore so generated HTML artifacts don’t end up committed.
• In docs/source/conf.py, you may want to set version/release dynamically from the project package instead of hardcoding '1.0' to avoid having to update this file on every release.
• The .readthedocs.yaml file pins Python to 3.7; if the project targets a different version in production, it would be safer to align this to the same Python version to avoid subtle discrepancies in behavior or dependencies.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Consider adding the Sphinx build output directory (e.g. `docs/build/`) to `.gitignore` so generated HTML artifacts don’t end up committed.
- In `docs/source/conf.py`, you may want to set `version`/`release` dynamically from the project package instead of hardcoding `'1.0'` to avoid having to update this file on every release.
- The `.readthedocs.yaml` file pins Python to 3.7; if the project targets a different version in production, it would be safer to align this to the same Python version to avoid subtle discrepancies in behavior or dependencies.

## Individual Comments

### Comment 1
<location path=".readthedocs.yaml" line_range="6" />
<code_context>
+build:
+  os: ubuntu-24.04
+  tools:
+    python: "3.7"
+
+sphinx:
</code_context>
<issue_to_address>
**🚨 issue (security):** Using Python 3.7 on Read the Docs may cause compatibility and security issues.

Since 3.7 is EOL and many tools/dependencies are dropping support for it, it’d be safer to use the same (newer) Python version here as the project’s runtime to avoid subtle behavior differences and future dependency breakage.
</issue_to_address>

### Comment 2
<location path="docs/source/presentation.rst" line_range="1" />
<code_context>
+Présentation du projet
+======================
+
</code_context>
<issue_to_address>
**issue (bug_risk):** Présence probable d’un BOM UTF-8 au début du fichier.

Ce marqueur peut provoquer des comportements inattendus avec certains outils. Merci de le supprimer afin que le fichier soit encodé en UTF-8 sans BOM, comme les autres.
</issue_to_address>

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[sourcery-ai]

🚨 issue (security): Using Python 3.7 on Read the Docs may cause compatibility and security issues.

Since 3.7 is EOL and many tools/dependencies are dropping support for it, it’d be safer to use the same (newer) Python version here as the project’s runtime to avoid subtle behavior differences and future dependency breakage.

[sourcery-ai]

issue (bug_risk): Présence probable d’un BOM UTF-8 au début du fichier.

Ce marqueur peut provoquer des comportements inattendus avec certains outils. Merci de le supprimer afin que le fichier soit encodé en UTF-8 sans BOM, comme les autres.