> Target audience is a big factor too, I think the article failed to emphasize this. And, secondly, the nature of what is being documented. Right, I'd say scr

> Target audience is a big factor too, I think the article failed to emphasize this. And, secondly, the nature of what is being documented. Right, I'd say screenshots are crucial for certain kinds of documentation and terribly amateurish for others. A guide walking you through a user journey in a UI should definitely have screenshots. But there should be "real" documentation for things like APIs - if the only kind of documentation that exists for an API is guides with screenshots, you end up with a bunch of useless "hello world + a feature" documentation that doesn't help you understand the big picture, or how features/options interact.