Hi Nevin, correct. ^^^^^^^^^^^^^^ yes, it is a composite-pattern, but there are not just those two components that might be put into a folder: - First of all it is possible to nest folders, to allow putting together related content. Furthermore folders are a kind of a namespace, so you might have pages with the same title in different folders. - There are other components available to be used with SmallWiki as extension. As an example some time ago I have written a component displaying a keyword-index of your wiki. A lot of other components (have been|are|will be) written during software design courses at the University of Bern and Brussels. Just to name a few examples: link collection, photo gallery, forum, address-book, calendar pages, rss viewer, ... Exactly, usually this is for things like you mention: jpg, gif, mp3, mpg, zip, pdf, doc, ... Actually it is also possible to upload a html-file to serve static pages/style-sheets ... For further information about the design, see the diagrams in the documentation: Smallwiki - Collaborative Content Management http://www.iam.unibe.ch/~scg/smallwiki/smallwiki.pdf Wikis have always been flat (WikiWorks has one level: Book -> Page, SWiki has two levels: Shelf -> Book -> Page) and in my opinion this has a lot of drawbacks. Therefor I decided to implement a real composite and this gives a lot of power to the users to organize their things. Of course it also adds some complexity, but I think today everybody is used to work with folders and files in their filesystem. After all, it is possible to use SmallWiki without creating any folder: just put everything into the root, but there will be a mess very soon ;) See the examples above. Cheers, Lukas -- Lukas Renggli http://renggli.freezope.org _______________________________________________ Seaside mailing list Seaside(a)lists.squeakfoundation.org http://lists.squeakfoundation.org/listinfo/seaside