I've been reading though a lot of documentation recently, and notice a few things about how information is typically formatted. I'm usually looking for information formated as facts or lists of facts. I figure I'm bright enough to string the facts together into actions. Tutorials are nice, but they kind of show the "drive-by" version. They don't always talk about why you do this or that, you get a single perspective on what is usually a multi-functional tool.
What do you find most useful? Do you want to know what the tools do, or do you just want to see some random example of them being used? Desk Reference or scripted tutorial? Several small, focused examples or one large example that covers a range of issues artificially linked together?
I know, I'm asking the question in an unfair way, but I'd just like to hear a few arguments one way and the other for different types of documentation. Examples of what you think good stuff looks like would be helpful. I guess I'm talking about professional "stuff" rather than homegrown.