Gradle's documentation falls into a trap that I find many projects falling into: thinking that, if you have documented all of the thing's parts, you have docume

Gradle's documentation falls into a trap that I find many projects falling into: thinking that, if you have documented all of the thing's parts, you have documented the whole thing. The only projects I see reliably escaping this trap are ones with commercial backing. I'm guessing the problem is that nobody does tech writing as a hobby, so, if you want to get good tech writing, you need to actually hire a tech writer.