I understand this is a new experiment. I tried earlier, to create a documentation for a web api .net prototype. All was honky dory until I got to the database, there is no way I'm gonna describe my database in a lowly md document.
This took me to realize that documentation itself cannot carry the whole weight of the description of a project, of any kind.
For databases and other resources, specific documents or even code and projects have to be uploaded so the agents can take real charge on them. Meanwhile, this is just good to prototype and tinker.
I looked for foreign documents that can be integrated to the documentation but didn't find anything.
What is the position of the team on this matter?
I understand this is a new experiment. I tried earlier, to create a documentation for a web api .net prototype. All was honky dory until I got to the database, there is no way I'm gonna describe my database in a lowly md document.
This took me to realize that documentation itself cannot carry the whole weight of the description of a project, of any kind.
For databases and other resources, specific documents or even code and projects have to be uploaded so the agents can take real charge on them. Meanwhile, this is just good to prototype and tinker.
I looked for foreign documents that can be integrated to the documentation but didn't find anything.
What is the position of the team on this matter?