Organization of documentation in automated testing. How to organize?

Question

Software testing

There is an existing project in Test Complite (more precisely 2 projects) with a complete lack of documentation.
Since there were only 2 automators and they were all from the beginning of the beginning of the introduction of autotests, this documentation didn’t matter to them. they themselves wrote it all and knew what and how it works. + there are several documents with instructions and descriptions of various processes within the project
Now I came to this project and getting acquainted with the project I learn everything by random. It would be desirable to structure it all in one file of the document.
What are the best ways to do this?
What we have now:
Several separate projects in Test Complite that contain test code
About 10 files explaining individual features, such as XML file settings
All tests are stored in common with the manuals in the TestLpg project

Answer 1

If I were you, I would first of all answer myself the question "What problem should the documentation you need solve."
Why do you want to write it?
What would the structure of the autotest project, its launch, etc. be more transparent for a new person?
To make it clear which cases are covered by autotests and which are not?
To make it clear exactly what actions and checks are performed in a particular autotest?
What if there was just documentation and everything was fine?
As soon as there is a list of specific problems that the documentation you want to solve - the choice of how the document you want to look like will be more obvious.