Hi Mathew,

This is something the noobs need badly. How about creating a community
documentation wiki like the RailsWiki
http://wiki.rubyonrails.org/rails
except it should be better organized by a team leader.
My thoughts on this...

I think it should have two broad sections.
1. Manuals
Howtos, tutorials and long winded explanations
2. Language reference
The links on ref.home should map to the classes as they are displayed
in the system browser. Categories -> Classes -> Methods. (no need for
method categories I think) Then for each method there should be a
brief explanation followed by example usage.

The skeleton can be setup by the team and the community can start
filling things in. Team would also do some editing of content...filter
out spam etc.(or require login - with email verification. RailsWiki
had some bad spam problems).

I'll be happy to participate and can even host it on my server.
my 2 cents worth.

bakki

On 9/21/06, Matthew Fulmer <tapplek at gmail.com> wrote:
> After some discussion with bmp on #squeak, I have decided to
> start writing a tutorial on squeak. bmp told me that the best
> way to proceed with this task is to take all the documentation
> available on the swiki [1] and massively refactor it into book
> form.
>
> I am a squeak noob, and I cannot do this alone. I have created
> an outline of my proposal [2] on the swiki. If you have a better
> idea, please say so. I really want to get involved with this
> amazing project. This will be a great way for us noobs to
> contribute and learn about squeak.
>
> [1] http://minnow.cc.gatech.edu/squeak
> [1] http://minnow.cc.gatech.edu/squeak/5870
>
> --
> Matthew Fulmer
>
>