One thing missed in the various discussions of documentation here is that the Haskell ecosystem is actually highly variable in both the amount of and need for v

One thing missed in the various discussions of documentation here is that the Haskell ecosystem is actually highly variable in both the amount of and need for various types of documentation. There's a pile of packages like diagrams (http://projects.haskell.org/diagrams/ http://projects.haskell.org/diagrams/) or yesod (http://www.yesodweb.com/ http://www.yesodweb.com/) which have tutorials, examples, books. People who have been working mainly with these should be completely expected not to feel much of a problem with the state of documentation. There are also packages which have mostly/only API information. Sometimes, this tells you everything you need to use a package effectively. Sometimes it doesn't. And this is impacted substantially by people's level of skill -- at Haskell and at inferring usage from names and type information in particular. There's room for people to have very different experiences