Thanx Sebastian, I was waiting since the beginning for your feedback. On Fri, May 28, 2010 at 3:53 PM, Sebastian Hennebrueder <[email protected]>wrote:
> Hi Robin, > > this is a great design and the first impression visiting the page is > amazing. Personally I prefer version 1 which remembers me of a magazin like > front page. > > When using version 4, the following case came into my mind. If you start > reading and the text starts to move away, you need to wait some time before > the slide reappears. > > From an information point of view, the front page is great. There is a > short introduction to tell the user what Tapestry is and some room for more > details. > > In an analysis I made some time ago for Tapestry, there had been different > types of users. You have already seen the remarks from the experienced > Tapestry users needing a direct link to documentation and probably news and > downloads. Another user type is the architect or CTO looking for quick > information of the project. He is interested in key features of Tapestry, > number of committers, support options, licence, release cycle, papers and > presentations > There is the new user who wants to learn the Tapestry and needs 'getting > started' infos, documentation, community areas and finally somebody who > wants to contribute. The latter needs information about contributing stands, > access to community. > > The links you have positioned on the top do not include community and > support. > > We do not refer to Apache as well. May be there is a place for a sentence > like ' Tapestry is an Apache Foundation project.' > > Below you can find a information grouping I made, when we have discussed > the redesign in 2009. > > I hope this time, we are going to succeed and get the main website updated. > > Go on guys and core committers don't let this effort silently die again. > > Best Regards > > Sebastian > > About the Project > > * Home > * Features > * Project Information > * Release Notes > * News > * Committer > * Contributions > * Sponsorship > * Thanks > > Getting started > > * Official Tutorial > * Screencasts > > Documentation > > * User Guide > * FAQ > * WIKI > * Component Reference > * Java Doc > * Nightly Java Doc > * Blogs of Committers > * Refcard - Tapestry on a single page > * Articles and Books > * Old Tapestry Documentation > > Support and Community > > * Mailinglist > * IRC Chat > * Issue Tracking > * Commercial Support > * Training > > Download > > * Binary and source downloads > * Offline Documentation > * Maven > * Subversion source repository > > Tapestry Modules and Components > > * tapestry5-annotations > * tapestry-core > * tapestry-hibernate > * tapestry-hibernate-core > * tapestry-ioc > * tapestry-spring > * tapestry-test > * tapestry-upload > * -- > * Third Party Libraries > * Tapestry 360 > > Contributing to Tapestry > > * Introduction > * Source Repository > * Environment > * Release checklist > * Bible > > > > > > Am 27.05.10 08:34, schrieb Christophe Cordenier: > > Hi >> >> This one may sound a bit old-fashioned nevertheless i suggest it : Build >> Once Compose Everywhere >> >> 2010/5/26 Thiago H. de Paula Figueiredo<[email protected]> >> >> On Wed, 26 May 2010 18:57:20 -0300, Christian Riedel< >>> [email protected]> wrote: >>> >>> Sounds like advertisement for some AOP-framework :) >>> >>>> >>>> >>> It could be Tapestry-IoC slogan, then. :) >>> >>> -- >>> Thiago H. de Paula Figueiredo >>> Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, >>> and instructor >>> Owner, Ars Machina Tecnologia da Informação Ltda. >>> http://www.arsmachina.com.br >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >>> >>> >> >> > > > -- > Best Regards / Viele Grüße > > Sebastian Hennebrueder > ----- > Software Developer and Trainer for Hibernate / Java Persistence > http://www.laliluna.de > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
