Most of the questions I've had to ask have already been asked by someone else. Therefore, usually the answer is "out there" for a search to find.
HOWEVER, I must correct a statement: it's not that there is a shortage of people who are willing to document linux: there is a shortage of people who understand the system well AND are any good at making documentation, and THEN there's few of them who want to be bothered with doing a whole week's worth of typing (that nobody will end up reading anyway).
The problem with "documentation" is, "document what"?
I mean, sure, someone could write a "configure your firewall" document, but people have written big, thick books about network theory, how the various protocols work, and the targets for what firewalls block are evolving.
One of the ongoing pains is Samba documentation, which is actually voluminous, but doesn't really help for most things, because nobody has bothered to simply provide a SAMBA front-end that looks and acts and configures just like the Windows file sharing, which it's for. Besides, every time a new version of Windows is released, M$ break Samba in some way that takes months to sort out. Fancy that.
At least MOST of my Linux problems have been sorted out by my not needing a dial-up connection. This was complicated by Linux distros like Redhat containing no fewer than THREE incompatible dial-up configurators, and no hint as to which was the appropriate one to use. A lot of linux's "Bad Rap" is all these clowns who package it up and sell it, and do a horrible job of it.
Provide ONE way to do everything, and document it thoroughly. If the user is adventurous, and wants to try other (custom) things, that's their own problem. For everyone else, the thing should work out of the box, and come with that "value added" documentation that can be seperately copyrighted and make their distro worth the money.
After all, you can freely download most versions of Linux as ISO images, without the technical support, manuals, etc.