> I agree with Tim and Matt that using comments would be great way to
> go, with one caveat :)
>
> The biggest frustration with using comments is that there is no good
> "starting place" for a given class category. For example, go browse
> the Seaside classes and categories and figure out where one should
> start. You can repeat this exercise for any number of categories. I
> propose that we we add a documentation attribute to the PackageInfo
> stuff, so there is a category level documentation spot, with links to
> the appropriate class comments.
>
> Any thoughts?

When I am trying to figure out which class in a class category is a good
starting point, I look at which class is the lowest in the inheritance
chain...

Cheers,
Tim