I have been thinking of doing that, at least to get google to index smalltalk code, so that people can see what that looks like without loading an image first. As far as structured documentation is concerned, you already have that from within smalltalk, when there are class or method comments.
There is already code in Pier to export comments as LaTeX or HTML code, I think that's what Lukas used to generate part of his thesis. SqueakSource has a code browser but it's not bookmarkable and I don't think it's indexed by search engines.
On 27/12/2007, Robert Hawley rhawley@plymouth.ac.uk wrote:
Documentation Suggestion.
Can we have direct links from within the Squeak image from each class, method, project, category, package, (etc.,) into a user-editable documentation web-site? It would effectively be Squeak's own encyclopedia; similar to wikipedia. Structured documentation could be available with great immediacy, be developed incrementally and be subject to continual review and rewrite by the whole community.
If there is existing discussion on this idea then it would be useful to have pointers to it. If it has not been much discussed before then I would suggest that this is a possibility worth exploring.
Yours
Bob