I think it's a really good idea. Currently the newcomer has to follow all the links to estimate what is more important and what is less important. That takes a lot of time.
On Thu, Aug 6, 2009 at 1:04 AM, Sebastian Hennebrueder <use...@laliluna.de>wrote: > Hello, > > while working on my Tapestry evaluation article, I start to like Tapestry > but get annoyed at the same time by the distribution of the documentation. > > Sofar I used the following sources linked from the main site > > Tapestry 5 Project > - JavaDocs > - Component Reference > - FAQ > Tapestry Tutorials > - Tutorial > User Guide > - many links here > Tapestry Cookbook > - some links > Resources > - WIKI > - WIKI howto > Junit Tests provided with the downloads (needed to read them as some > components are not documented) > > This is pretty hard for a new user. > > What do you think about the following structure? > Getting started > - Installation with Maven > - Installation without Maven > - Quick start tutorial > - Screen casts > Documentation > - User Guide > - Component Reference > - Java Doc > - FAQ > - Ref card > Documentation by the community > - WIKI > - WIKI Howtos > > merge the content of the cookbook into the user guide or the wiki howto > > -- > Best Regards / Viele Grüße > > Sebastian Hennebrueder > ----- > Software Developer and Trainer for Hibernate / Java Persistence > http://www.laliluna.de > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
