Indeed. Code describes
how something is done, and possibly
what is done, but it seldom fully describes
why something is done, or why code exists in the first place.
The latter is typically the realm of requirements, design documentation, and possibly test plans.
Generating such documentation from code seems quite impossible, or at least wrong.
It is unfortunate that most open source software is lacking in such documentation, giving off bad signals to junior developers.
Edit: not to take away from the product being discussed here, which seems very useful! I am merely supporting the parent here.
The latter is typically the realm of requirements, design documentation, and possibly test plans.
Generating such documentation from code seems quite impossible, or at least wrong.
It is unfortunate that most open source software is lacking in such documentation, giving off bad signals to junior developers.
Edit: not to take away from the product being discussed here, which seems very useful! I am merely supporting the parent here.