[racket] How to document a package and access its documentation

A few minutes ago, Vincent St-Amour wrote:
> I don't think documentation format is really a big problem, as long
> as it's human-readable. How to find it in the first place is the big
> problem IMO.

Yes, that comes first, of course.  It's a problem of making it easy to
do exactly the kind of package shopping that people want to do -- and
there's a range of:

  1 Nothing more than a source link
  2 Link to docs
  3 Standard docs
  4 Standard + searchable docs
  5 ... which are available in drr

So the goal should be to reach the top of this range.  (But obviously
it shouldn't be hard to generate the docs for authors.)

-- 
          ((lambda (x) (x x)) (lambda (x) (x x)))          Eli Barzilay:
                    http://barzilay.org/                   Maze is Life!