Currently, the documentation for the frontend is incomplete, scattered in several places and hard to find. This makes onboarding for new developers difficult, as we use several in-house libraries (such as Reactix and Toestand) that developers need to be familiar with before they can contribute.

I think the following steps could help alleviate the issue:

• Create a new centralized documentation repository, maybe hosted at docs.gargantext.org, built using something like mkdocs. This should be linked prominently in the project readme to be easy to find.

The documentation could include the following:

• A reference of Reactix and Toestand, including examples and comparisons to vanilla JS/TS and React to help developer familiarity
• An explanation of some of the architectural decisions and coding best practices
• An explanation of the testing framework (when implemented)

In the future, this could also be extended to document the backend, and matters such as contribution guidelines etc.

An alternative could be hosting the documentation on gargantext itself but that might create barriers for access and editing (vs being built from markdown files in a git repo)