Sure, keep documentation about code in the source code. Where exactly in the source code does your tutorial go?
You seem to be reading into a lot of things that aren't in the article based on what you want to hear.
vi(1)
emacs(1)
firefox(1)
google-chrome(1)
Microsoft Word or Internet Explorer, if that's your thing!
As for "where does your tutorial go," see for example "Control.Pipes.Tutorial".
http://hackage.haskell.org/package/pipes-4.0.0/docs/Pipes-Tu...
If someone can't figure these things out, by all means, go use someone else's library. This sort of documentation would not be acceptable for a consumer product like TurboTax, but a programmer needs to know how to view a text file.
What's better, the docs for Backbone.Marionette[0], or Backbone[1]?
[0]: https://github.com/marionettejs/backbone.marionette/tree/mas... [1]: http://backbonejs.org/
Offline or online viewing? Should I need a web connection to read the documentation?