Agree to all of that. Fantastic analysis Sebastian.
The whole documentation should revolve around Tapestry 5.x, and make it clear, an easy snapshot of what the framework looks like. Then more detailed information on demand. Michael Gerzabek wrote: > > Sebastian, great job! The main point is your thesis of missing 50 to 80 > percent of potential new customers. What a waste of time and brainpower!!! > > I completely agree in selling the stuff to new users. This could as you > pointed out very elegantly with rather small changes in the structure > and graphical design. > > Anyway. What I see as an urgent need though are some high level > architecture overviews like the one of the component rendering [1]. For > example what was hard to learn for me was the concept of how the request > ist processed. A single picture of the different cycles of > render-request and action-request (and when what setup is important and > how achieved) would solve a lot of problems. And I'm sure there are many > other concepts as well. > > Kudos Sebastian! > > Michael > > [1] http://tapestry.apache.org/tapestry5.1/guide/rendering.html > -- View this message in context: http://n2.nabble.com/Website-concept-tp3619168p3624505.html Sent from the Tapestry Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
