At this point, I would say everything you know about.  I mean, the stuff on 
squeak.org and whysmalltalk.com I have tracked down, but I am sure you have 
spots you go to that I am not aware of.

If the information is too much we can take a time out and go through and 
classify it.  But we will need all levels of documentation before we are 
finished.


>From: "Ralph Johnson" <johnson at cs.uiuc.edu>
>Reply-To: The general-purpose Squeak developers 
>list<squeak-dev at lists.squeakfoundation.org>
>To: "The general-purpose Squeak developers 
>list"<squeak-dev at lists.squeakfoundation.org>
>Subject: Re: Request for links (was: [ANN] Squeak Documentation Project)
>Date: Sun, 24 Sep 2006 07:46:10 -0500
>
>>One of the deliverables from the Documentation project is a comprehensive
>>index of available documentation.  So if everyone who knows of some
>>not-so-well-known documentation please send it.  If you don't want to put 
>>it
>>on the list you can send it to Mathew and myself.
>
>What do you mean by "documentation"?  One reason that documentation is
>a problem is that so much has been written, but some of it is
>advanced, some of it is for Smalltalk in general, which might or might
>not be applicable, some of it is old and no longer 100% correct, some
>of it is written in mailing lists rather than as formal documents.  Do
>you want lecture notes, documentation for particular packages, videos?
>
>My guess is that the best way to find what is relevant is to do what
>you are doing, i.e. to ask questions and to see which documents you
>are given for answers.
>
>-Ralph
>