You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by Robin Komiwes <ro...@gmail.com> on 2010/05/25 12:06:03 UTC
[DISCUSS] Tapestry homepage redesign
I said some weeks ago that I will assist the documentation renew effort by
proposing a redesign for Tapestry homepage.
I'm quite satisfied with the first draft and I now need the community
feedback to know if I should stop or continue this way. Of course, if
someone wants to help on the content or the design, you are very welcome.
The URLs :
http://komiwes.fr/tapestry
http://komiwes.fr/tapestry/getting_started.htm
http://komiwes.fr/tapestry/community.htm
Now, here are the key principles of this redesign. I've tried to follow
them, and some may need to be expressed more.
- Everything is marketing
Others frameworks understand that well. They all have a shiny homepage, with
key words, quotes from great people and baselines that you can't miss.
The homepage should seduce and convince people. You've got to know that the
framework you are using, or about to, is one of the best frameworks. In
fact, there are plenty of good frameworks, if you launch tomorrow another
"good framework", you are already dead. You need to offer a rockstar
framework.
On this redesign, a newcomer will be satisfied by how the information is
clear and concise. He will know the concept of Tapestry (cf baseline) and
will instantly have an idea of Tapestry strengths (cf Java power, scripting
ease, highly productive).
Finally he will be invited to give 20 minutes of its time to try the
framework and realize how true was what we announced before.
- Community
Every framework should focus on its community. IMHO, that's another key
point: again, if you think that an open source framework will buzz just
because it is well made, you may have miss how the internet has evolved
since some years. Ruby on Rails and jQuery have integrated that since the
beginning. Focusing on the community is mandatory. Why?
First, because as a Web framework developer, you can't cover every feature.
Web is just too big. Especially in the Java ecosystem. If someone cover a
feature for you, thanks him and then do advertising for its contribution as
it was one of the features of the framework. It should be presented as a
part of the framework itself, not as "a nice side project that you may look
to if you want to...".
Secondly, because the web is social. If people feels that they are part of
an active community, they will be proud of it and will wants to make other
people joining it. They will blog for you, they will evangelize for you. In
fact, they will to the marketing job for you.
I think the effort on this point should be pushed a lot further. We should
have some specs on how to write and provide components library, how to
provides plugins. We should have a place where to publish them.
We should also have an open sourced keynote available to make presentations
of Tapestry 5, like Howard's one :
http://www.slideshare.net/hlship/tapestry-5-java-power-scripting-ease
Everyone should be able to grab it and then do a presentation to its local
JUG.
- Fresh content
It's important to look like active. We all know here that Tapestry is active
but if you look at the actual website, there is no clue about that.
Here, I think using a specific Twitter account (I've reserved @tapestry_5)
for pushing news both on a social network and on the Tapestry website would
be great. We would be able to easily push fresh, concise news from both
Tapestry 5 framework and any other related tweets.
- Efficiency
One of the "cons" of maven sites is that they make you writing big pages and
big menus. It is bad because it results in an insanely big amount of data
that kills the data itself.
The homepage should be efficient and concise.
- References
Real Tapestry applications showcase is a must have. We should be able to say
"Hey, look! They've been using Tapestry in production and see how nice it
works.". We already have some greats examples and we should show them.
Re: [DISCUSS] Tapestry homepage redesign
Posted by "Thiago H. de Paula Figueiredo" <th...@gmail.com>.
On Wed, 26 May 2010 14:41:21 -0300, Christian Edward Gruber
<ch...@gmail.com> wrote:
> Heh. I like it. Another I like is "Tapestry: Code Less, Deliver More"
I like it! :) Or maybe "Tapestry: implement more with less code".
--
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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [DISCUSS] Tapestry homepage redesign
Posted by Christian Edward Gruber <ch...@gmail.com>.
Heh. I like it. Another I like is "Tapestry: Code Less, Deliver More"
Christian.
On May 26, 2010, at 1:15 PM, Howard Lewis Ship wrote:
> "Why build when you can weave?" :-}
>
> On Wed, May 26, 2010 at 10:05 AM, Christophe Cordenier
> <ch...@gmail.com> wrote:
>> Hi
>>
>>
>> Le 26 mai 2010 à 18:46, "Thiago H. de Paula Figueiredo" <thiagohp@gmail.com
>> >
>> a écrit :
>>
>>> On Wed, 26 May 2010 12:27:31 -0300, Christophe Cordenier
>>> <ch...@gmail.com> wrote:
>>>
>>>> As i am already a big fan of Robin's work, my opinion won't be much
>>>> objective :)
>>>>
>>>> I have only one suggestion, A subtitle would be nice to express the
>>>> Tapestry philosophy. I have though to 'Compose your Web
>>>> Application'
>>>
>>> A slogan for Tapestry? Hum, nice idea! But I don't think 'Compose
>>> your Web
>>> Application' is good enough . . .
>>>
>>> This remembers something I read once: "Tapestry is what JSF should
>>> have
>>> been". :P
>>
>> Ahah i Will remember this one next time i do a training and someone
>> ask me
>> why tapestry and not jsf ?
>>
>>>
>>>> Development is Art !
>>>
>>> I agree 1000%. That's why my little company is named Ars Machina
>>> (ars =
>>> art, machina = machine)
>>>
>>> --
>>> 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: dev-unsubscribe@tapestry.apache.org
>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>
>>
>
>
>
> --
> Howard M. Lewis Ship
>
> Creator of Apache Tapestry
>
> The source for Tapestry training, mentoring and support. Contact me to
> learn how I can get you up and productive in Tapestry fast!
>
> (971) 678-5210
> http://howardlewisship.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [DISCUSS] Tapestry homepage redesign
Posted by Kalle Korhonen <ka...@gmail.com>.
On Fri, Jul 9, 2010 at 2:34 AM, Robin Komiwes <ro...@gmail.com> wrote:
> Here is the URL for the previews:
> http://komiwes.fr/www-tapestry/
> What do you think?
I'm almost afraid to comment since I'm certainly no expert on UI
issues and I'm not sure that designing an UI by a committee works
well, but to me, the contrast between white and black is too strong. I
wonder if a lighter shade of gray for the background would be better
(though it easily becomes too boring and Windows UI like).
The other thing, and this might deserve its own thread, but doesn't
anybody else feel that "code less, deliver more" is overused to a
point it sounds almost childish. I'd much rather see something simpler
and more elegant such:
Tapestry 5 - Code Less.
Tapestry 5 - Deliver.
Tapestry 5 - Deliver the Web
Tapestry 5 - Express the Web
Tapestry 5 - Complete the Web
While you can do all sorts of things with Tapestry, the focus is still
on building web applications. I do admire all the efforts that you
guys, Uli and Robin and others, have put into this so far.
Kalle
> On Fri, May 28, 2010 at 3:57 PM, Robin Komiwes <ro...@gmail.com>wrote:
>
>> Thanx Sebastian, I was waiting since the beginning for your feedback.
>>
>>
>> On Fri, May 28, 2010 at 3:53 PM, Sebastian Hennebrueder <
>> usenet@laliluna.de> 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<th...@gmail.com>
>>>>
>>>> On Wed, 26 May 2010 18:57:20 -0300, Christian Riedel<
>>>>> cr.mlist@googlemail.com> 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: dev-unsubscribe@tapestry.apache.org
>>>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Best Regards / Viele Grüße
>>>
>>> Sebastian Hennebrueder
>>> -----
>>> Software Developer and Trainer for Hibernate / Java Persistence
>>> http://www.laliluna.de
>>>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>
>>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [DISCUSS] Tapestry homepage redesign
Posted by Ulrich Stärk <ul...@spielviel.de>.
That's exactly what I had in mind and merging ioc and other submodule documentation into the rest is
one of my tasks for the next days.
Uli
On 09.07.2010 17:26, Howard Lewis Ship wrote:
> This is making me very happy and I'm getting very, very excited about
> the documentation rework. To me, this is a reboot of the Tapestry
> brand as much as T5 was a reboot of the code.
>
> One thing that occurs to me as we work on and refactor the
> documentation is that the distinction between tapesry-ioc and
> tapestry-core probably causes some confusion. I think we should treat
> Tapestry as all on unit, and have extra notes and pages to discuss
> using IoC without the rest of Tapestry. Likewise, the Hibernate
> support, etc. For stuff that builds on top of tapestry-core, an easy
> macro to identify which module(s) contribute
> the described behavior.
>
> On Fri, Jul 9, 2010 at 4:14 AM, Ulrich Stärk<ul...@spielviel.de> wrote:
>> Nice. Really nice. What I'm missing is the referenca to Apache. As I said
>> before, I think this should be reflected in the logo slogan (Apache Tapestry
>> 5). There should also be a full stop after "Code less, deliver more".
>>
>> Robin, can you please as quickly as possible make available the logo (also
>> the source) as well as the needed CSS? I'd really like to put up the new
>> website at [1] and start filling it with content so that we can finish this
>> project.
>>
>> Cheers,
>>
>> Uli
>>
>> [1] https://cwiki.apache.org/TAPESTRY/
>>
>> On 09.07.2010 11:49, Robin Komiwes wrote:
>>>
>>> fixed.
>>>
>>> -- Robin Komiwes
>>> On Fri, Jul 9, 2010 at 11:46 AM, Dmitry
>>> Gusev<dm...@gmail.com>wrote:
>>>
>>>> This looks relly cool.
>>>> Will the design fit to width or it will be fixed-width?
>>>>
>>>> One thing about documentation, will it have some structured TOC?
>>>>
>>>> On Fri, Jul 9, 2010 at 13:34, Robin Komiwes<ro...@gmail.com>
>>>> wrote:
>>>>
>>>>> Not satisfied with my first proposals, I was waiting for new inspiration
>>>>
>>>> to
>>>>>
>>>>> come in order to propose something better.
>>>>> That happened yesterday in the train, on the return of a tapestry5
>>>>
>>>> training
>>>>>
>>>>> I gave.
>>>>> Here is the URL for the previews:
>>>>> http://komiwes.fr/www-tapestry/
>>>>>
>>>>> What do you think?
>>>>> -- Robin Komiwes
>>>>> On Fri, May 28, 2010 at 3:57 PM, Robin Komiwes<robin.komiwes@gmail.com
>>>>>>
>>>>>> wrote:
>>>>>
>>>>>> Thanx Sebastian, I was waiting since the beginning for your feedback.
>>>>>>
>>>>>>
>>>>>> On Fri, May 28, 2010 at 3:53 PM, Sebastian Hennebrueder<
>>>>>> usenet@laliluna.de> 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<th...@gmail.com>
>>>>>>>>
>>>>>>>> On Wed, 26 May 2010 18:57:20 -0300, Christian Riedel<
>>>>>>>>>
>>>>>>>>> cr.mlist@googlemail.com> 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: dev-unsubscribe@tapestry.apache.org
>>>>>>>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Best Regards / Viele Grüße
>>>>>>>
>>>>>>> Sebastian Hennebrueder
>>>>>>> -----
>>>>>>> Software Developer and Trainer for Hibernate / Java Persistence
>>>>>>> http://www.laliluna.de
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>>>>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Dmitry Gusev
>>>>
>>>> AnjLab Team
>>>> http://anjlab.com
>>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>
>>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [DISCUSS] Tapestry homepage redesign
Posted by Howard Lewis Ship <hl...@gmail.com>.
This is making me very happy and I'm getting very, very excited about
the documentation rework. To me, this is a reboot of the Tapestry
brand as much as T5 was a reboot of the code.
One thing that occurs to me as we work on and refactor the
documentation is that the distinction between tapesry-ioc and
tapestry-core probably causes some confusion. I think we should treat
Tapestry as all on unit, and have extra notes and pages to discuss
using IoC without the rest of Tapestry. Likewise, the Hibernate
support, etc. For stuff that builds on top of tapestry-core, an easy
macro to identify which module(s) contribute
the described behavior.
On Fri, Jul 9, 2010 at 4:14 AM, Ulrich Stärk <ul...@spielviel.de> wrote:
> Nice. Really nice. What I'm missing is the referenca to Apache. As I said
> before, I think this should be reflected in the logo slogan (Apache Tapestry
> 5). There should also be a full stop after "Code less, deliver more".
>
> Robin, can you please as quickly as possible make available the logo (also
> the source) as well as the needed CSS? I'd really like to put up the new
> website at [1] and start filling it with content so that we can finish this
> project.
>
> Cheers,
>
> Uli
>
> [1] https://cwiki.apache.org/TAPESTRY/
>
> On 09.07.2010 11:49, Robin Komiwes wrote:
>>
>> fixed.
>>
>> -- Robin Komiwes
>> On Fri, Jul 9, 2010 at 11:46 AM, Dmitry
>> Gusev<dm...@gmail.com>wrote:
>>
>>> This looks relly cool.
>>> Will the design fit to width or it will be fixed-width?
>>>
>>> One thing about documentation, will it have some structured TOC?
>>>
>>> On Fri, Jul 9, 2010 at 13:34, Robin Komiwes<ro...@gmail.com>
>>> wrote:
>>>
>>>> Not satisfied with my first proposals, I was waiting for new inspiration
>>>
>>> to
>>>>
>>>> come in order to propose something better.
>>>> That happened yesterday in the train, on the return of a tapestry5
>>>
>>> training
>>>>
>>>> I gave.
>>>> Here is the URL for the previews:
>>>> http://komiwes.fr/www-tapestry/
>>>>
>>>> What do you think?
>>>> -- Robin Komiwes
>>>> On Fri, May 28, 2010 at 3:57 PM, Robin Komiwes<robin.komiwes@gmail.com
>>>>>
>>>>> wrote:
>>>>
>>>>> Thanx Sebastian, I was waiting since the beginning for your feedback.
>>>>>
>>>>>
>>>>> On Fri, May 28, 2010 at 3:53 PM, Sebastian Hennebrueder<
>>>>> usenet@laliluna.de> 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<th...@gmail.com>
>>>>>>>
>>>>>>> On Wed, 26 May 2010 18:57:20 -0300, Christian Riedel<
>>>>>>>>
>>>>>>>> cr.mlist@googlemail.com> 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: dev-unsubscribe@tapestry.apache.org
>>>>>>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Best Regards / Viele Grüße
>>>>>>
>>>>>> Sebastian Hennebrueder
>>>>>> -----
>>>>>> Software Developer and Trainer for Hibernate / Java Persistence
>>>>>> http://www.laliluna.de
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>>>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> Dmitry Gusev
>>>
>>> AnjLab Team
>>> http://anjlab.com
>>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!
(971) 678-5210
http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [DISCUSS] Tapestry homepage redesign
Posted by Ulrich Stärk <ul...@spielviel.de>.
Nice. Really nice. What I'm missing is the referenca to Apache. As I said before, I think this
should be reflected in the logo slogan (Apache Tapestry 5). There should also be a full stop after
"Code less, deliver more".
Robin, can you please as quickly as possible make available the logo (also the source) as well as
the needed CSS? I'd really like to put up the new website at [1] and start filling it with content
so that we can finish this project.
Cheers,
Uli
[1] https://cwiki.apache.org/TAPESTRY/
On 09.07.2010 11:49, Robin Komiwes wrote:
> fixed.
>
> -- Robin Komiwes
> On Fri, Jul 9, 2010 at 11:46 AM, Dmitry Gusev<dm...@gmail.com>wrote:
>
>> This looks relly cool.
>> Will the design fit to width or it will be fixed-width?
>>
>> One thing about documentation, will it have some structured TOC?
>>
>> On Fri, Jul 9, 2010 at 13:34, Robin Komiwes<ro...@gmail.com>
>> wrote:
>>
>>> Not satisfied with my first proposals, I was waiting for new inspiration
>> to
>>> come in order to propose something better.
>>> That happened yesterday in the train, on the return of a tapestry5
>> training
>>> I gave.
>>> Here is the URL for the previews:
>>> http://komiwes.fr/www-tapestry/
>>>
>>> What do you think?
>>> -- Robin Komiwes
>>> On Fri, May 28, 2010 at 3:57 PM, Robin Komiwes<robin.komiwes@gmail.com
>>>> wrote:
>>>
>>>> Thanx Sebastian, I was waiting since the beginning for your feedback.
>>>>
>>>>
>>>> On Fri, May 28, 2010 at 3:53 PM, Sebastian Hennebrueder<
>>>> usenet@laliluna.de> 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<th...@gmail.com>
>>>>>>
>>>>>> On Wed, 26 May 2010 18:57:20 -0300, Christian Riedel<
>>>>>>> cr.mlist@googlemail.com> 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: dev-unsubscribe@tapestry.apache.org
>>>>>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Best Regards / Viele Grüße
>>>>>
>>>>> Sebastian Hennebrueder
>>>>> -----
>>>>> Software Developer and Trainer for Hibernate / Java Persistence
>>>>> http://www.laliluna.de
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>>>
>>>>>
>>>>
>>>
>>
>>
>>
>> --
>> Dmitry Gusev
>>
>> AnjLab Team
>> http://anjlab.com
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [DISCUSS] Tapestry homepage redesign
Posted by Robin Komiwes <ro...@gmail.com>.
fixed.
-- Robin Komiwes
On Fri, Jul 9, 2010 at 11:46 AM, Dmitry Gusev <dm...@gmail.com>wrote:
> This looks relly cool.
> Will the design fit to width or it will be fixed-width?
>
> One thing about documentation, will it have some structured TOC?
>
> On Fri, Jul 9, 2010 at 13:34, Robin Komiwes <ro...@gmail.com>
> wrote:
>
> > Not satisfied with my first proposals, I was waiting for new inspiration
> to
> > come in order to propose something better.
> > That happened yesterday in the train, on the return of a tapestry5
> training
> > I gave.
> > Here is the URL for the previews:
> > http://komiwes.fr/www-tapestry/
> >
> > What do you think?
> > -- Robin Komiwes
> > On Fri, May 28, 2010 at 3:57 PM, Robin Komiwes <robin.komiwes@gmail.com
> > >wrote:
> >
> > > Thanx Sebastian, I was waiting since the beginning for your feedback.
> > >
> > >
> > > On Fri, May 28, 2010 at 3:53 PM, Sebastian Hennebrueder <
> > > usenet@laliluna.de> 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<th...@gmail.com>
> > >>>
> > >>> On Wed, 26 May 2010 18:57:20 -0300, Christian Riedel<
> > >>>> cr.mlist@googlemail.com> 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: dev-unsubscribe@tapestry.apache.org
> > >>>> For additional commands, e-mail: dev-help@tapestry.apache.org
> > >>>>
> > >>>>
> > >>>>
> > >>>
> > >>>
> > >>
> > >>
> > >> --
> > >> Best Regards / Viele Grüße
> > >>
> > >> Sebastian Hennebrueder
> > >> -----
> > >> Software Developer and Trainer for Hibernate / Java Persistence
> > >> http://www.laliluna.de
> > >>
> > >>
> > >>
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> > >> For additional commands, e-mail: dev-help@tapestry.apache.org
> > >>
> > >>
> > >
> >
>
>
>
> --
> Dmitry Gusev
>
> AnjLab Team
> http://anjlab.com
>
Re: [DISCUSS] Tapestry homepage redesign
Posted by Dmitry Gusev <dm...@gmail.com>.
This looks relly cool.
Will the design fit to width or it will be fixed-width?
One thing about documentation, will it have some structured TOC?
On Fri, Jul 9, 2010 at 13:34, Robin Komiwes <ro...@gmail.com> wrote:
> Not satisfied with my first proposals, I was waiting for new inspiration to
> come in order to propose something better.
> That happened yesterday in the train, on the return of a tapestry5 training
> I gave.
> Here is the URL for the previews:
> http://komiwes.fr/www-tapestry/
>
> What do you think?
> -- Robin Komiwes
> On Fri, May 28, 2010 at 3:57 PM, Robin Komiwes <robin.komiwes@gmail.com
> >wrote:
>
> > Thanx Sebastian, I was waiting since the beginning for your feedback.
> >
> >
> > On Fri, May 28, 2010 at 3:53 PM, Sebastian Hennebrueder <
> > usenet@laliluna.de> 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<th...@gmail.com>
> >>>
> >>> On Wed, 26 May 2010 18:57:20 -0300, Christian Riedel<
> >>>> cr.mlist@googlemail.com> 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: dev-unsubscribe@tapestry.apache.org
> >>>> For additional commands, e-mail: dev-help@tapestry.apache.org
> >>>>
> >>>>
> >>>>
> >>>
> >>>
> >>
> >>
> >> --
> >> Best Regards / Viele Grüße
> >>
> >> Sebastian Hennebrueder
> >> -----
> >> Software Developer and Trainer for Hibernate / Java Persistence
> >> http://www.laliluna.de
> >>
> >>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> >> For additional commands, e-mail: dev-help@tapestry.apache.org
> >>
> >>
> >
>
--
Dmitry Gusev
AnjLab Team
http://anjlab.com
Re: [DISCUSS] Tapestry homepage redesign
Posted by "Thiago H. de Paula Figueiredo" <th...@gmail.com>.
On Fri, 09 Jul 2010 06:34:36 -0300, Robin Komiwes
<ro...@gmail.com> wrote:
> Not satisfied with my first proposals, I was waiting for new inspiration
> to come in order to propose something better.
> That happened yesterday in the train, on the return of a tapestry5
> training I gave. Here is the URL for the previews:
> http://komiwes.fr/www-tapestry/
> What do you think?
Looks very good! :)
--
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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [DISCUSS] Tapestry homepage redesign
Posted by Robin Komiwes <ro...@gmail.com>.
Not satisfied with my first proposals, I was waiting for new inspiration to
come in order to propose something better.
That happened yesterday in the train, on the return of a tapestry5 training
I gave.
Here is the URL for the previews:
http://komiwes.fr/www-tapestry/
What do you think?
-- Robin Komiwes
On Fri, May 28, 2010 at 3:57 PM, Robin Komiwes <ro...@gmail.com>wrote:
> Thanx Sebastian, I was waiting since the beginning for your feedback.
>
>
> On Fri, May 28, 2010 at 3:53 PM, Sebastian Hennebrueder <
> usenet@laliluna.de> 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<th...@gmail.com>
>>>
>>> On Wed, 26 May 2010 18:57:20 -0300, Christian Riedel<
>>>> cr.mlist@googlemail.com> 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: dev-unsubscribe@tapestry.apache.org
>>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>> --
>> Best Regards / Viele Grüße
>>
>> Sebastian Hennebrueder
>> -----
>> Software Developer and Trainer for Hibernate / Java Persistence
>> http://www.laliluna.de
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>
>>
>
Re: [DISCUSS] Tapestry homepage redesign
Posted by Robin Komiwes <ro...@gmail.com>.
Thanx Sebastian, I was waiting since the beginning for your feedback.
On Fri, May 28, 2010 at 3:53 PM, Sebastian Hennebrueder
<us...@laliluna.de>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<th...@gmail.com>
>>
>> On Wed, 26 May 2010 18:57:20 -0300, Christian Riedel<
>>> cr.mlist@googlemail.com> 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: dev-unsubscribe@tapestry.apache.org
>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>
>>>
>>>
>>
>>
>
>
> --
> Best Regards / Viele Grüße
>
> Sebastian Hennebrueder
> -----
> Software Developer and Trainer for Hibernate / Java Persistence
> http://www.laliluna.de
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
Re: [DISCUSS] Tapestry homepage redesign
Posted by Sebastian Hennebrueder <us...@laliluna.de>.
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<th...@gmail.com>
>
>> On Wed, 26 May 2010 18:57:20 -0300, Christian Riedel<
>> cr.mlist@googlemail.com> 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: dev-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>
>>
>
>
--
Best Regards / Viele Grüße
Sebastian Hennebrueder
-----
Software Developer and Trainer for Hibernate / Java Persistence
http://www.laliluna.de
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [DISCUSS] Tapestry homepage redesign
Posted by Christophe Cordenier <ch...@gmail.com>.
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 <th...@gmail.com>
> On Wed, 26 May 2010 18:57:20 -0300, Christian Riedel <
> cr.mlist@googlemail.com> 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: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
--
Regards,
Christophe Cordenier.
Developer of wooki @wookicentral.com
Re: [DISCUSS] Tapestry homepage redesign
Posted by "Thiago H. de Paula Figueiredo" <th...@gmail.com>.
On Wed, 26 May 2010 18:57:20 -0300, Christian Riedel
<cr...@googlemail.com> 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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [DISCUSS] Tapestry homepage redesign
Posted by Christian Riedel <cr...@googlemail.com>.
Sounds like advertisement for some AOP-framework :)
Am 26.05.2010 um 20:28 schrieb Piero Sartini:
> 2010/5/26 Howard Lewis Ship <hl...@gmail.com>:
>> "Why build when you can weave?" :-}
>
> I like it!
> Some variations: "Weave the web!", "Weave your source!", "Weave your apps!"
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [DISCUSS] Tapestry homepage redesign
Posted by Piero Sartini <li...@pierosartini.de>.
2010/5/26 Howard Lewis Ship <hl...@gmail.com>:
> "Why build when you can weave?" :-}
I like it!
Some variations: "Weave the web!", "Weave your source!", "Weave your apps!"
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [DISCUSS] Tapestry homepage redesign
Posted by Howard Lewis Ship <hl...@gmail.com>.
"Why build when you can weave?" :-}
On Wed, May 26, 2010 at 10:05 AM, Christophe Cordenier
<ch...@gmail.com> wrote:
> Hi
>
>
> Le 26 mai 2010 à 18:46, "Thiago H. de Paula Figueiredo" <th...@gmail.com>
> a écrit :
>
>> On Wed, 26 May 2010 12:27:31 -0300, Christophe Cordenier
>> <ch...@gmail.com> wrote:
>>
>>> As i am already a big fan of Robin's work, my opinion won't be much
>>> objective :)
>>>
>>> I have only one suggestion, A subtitle would be nice to express the
>>> Tapestry philosophy. I have though to 'Compose your Web Application'
>>
>> A slogan for Tapestry? Hum, nice idea! But I don't think 'Compose your Web
>> Application' is good enough . . .
>>
>> This remembers something I read once: "Tapestry is what JSF should have
>> been". :P
>
> Ahah i Will remember this one next time i do a training and someone ask me
> why tapestry and not jsf ?
>
>>
>>> Development is Art !
>>
>> I agree 1000%. That's why my little company is named Ars Machina (ars =
>> art, machina = machine)
>>
>> --
>> 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: dev-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!
(971) 678-5210
http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [DISCUSS] Tapestry homepage redesign
Posted by Christophe Cordenier <ch...@gmail.com>.
Hi
Le 26 mai 2010 à 18:46, "Thiago H. de Paula Figueiredo" <thiagohp@gmail.co
m> a écrit :
> On Wed, 26 May 2010 12:27:31 -0300, Christophe Cordenier <christophe.cordenier@gmail.com
> > wrote:
>
>> As i am already a big fan of Robin's work, my opinion won't be much
>> objective :)
>>
>> I have only one suggestion, A subtitle would be nice to express the
>> Tapestry philosophy. I have though to 'Compose your Web Application'
>
> A slogan for Tapestry? Hum, nice idea! But I don't think 'Compose
> your Web Application' is good enough . . .
>
> This remembers something I read once: "Tapestry is what JSF should
> have been". :P
Ahah i Will remember this one next time i do a training and someone
ask me why tapestry and not jsf ?
>
>> Development is Art !
>
> I agree 1000%. That's why my little company is named Ars Machina
> (ars = art, machina = machine)
>
> --
> 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: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [DISCUSS] Tapestry homepage redesign
Posted by Robin Komiwes <ro...@gmail.com>.
I mean the text won't go over a centered portion of 1000px. It's a styling
effect to let some graphics going all over the screen.
On Thu, May 27, 2010 at 10:56 AM, Ulrich Stärk <ul...@spielviel.de> wrote:
> No they are not. In No. 2, 3 and 4 the green bar extends over the whole
> page width, and in 2 the green backgroud image in the banner does as well.
>
> Uli
>
>
> On 27.05.2010 10:21, Robin Komiwes wrote:
>
>> Yes Ulrich, you're right, there is something odd with the gradient and it
>> should be replaced. I'll fix that when the new logo will be ready.
>>
>> Just to be sure, all layouts are fixed, it's just that there is no border
>> anymore. I do prefer 3 and 4, but I can't make my choice between the
>> classic
>> version and the slider version.
>>
>> On Thu, May 27, 2010 at 9:29 AM, Ulrich Stärk<ul...@spielviel.de> wrote:
>>
>> I still like No. 1 best. That's probably because of my preference for
>>> fixed-width layouts. The content area is clearly delimited by the shadow
>>> border, the key features are all visible at once and it's not obtrusive.
>>> The
>>> banner might need some more tweaking, something feels odd about the green
>>> background image, but I can't put a finger on it.
>>>
>>> Cheers,
>>>
>>> Uli
>>>
>>>
>>> On 26.05.2010 18:58, Robin Komiwes wrote:
>>>
>>> Fun :) On the first versions of Wooki, the title of the sample book when
>>>> launching the application was :
>>>> "Tapestry 5 : When development meets Art"
>>>>
>>>>
>>>> http://github.com/robink/wooki/blob/7a3aaa0a9bd87856cab45fa1a012424423d9093d/src/main/java/com/wooki/services/StartupServiceImpl.java
>>>>
>>>>
>>>> By the way, the first draft have moved.
>>>> I'll now make new proposals by adding them into a subfolders
>>>> Check http://komiwes.fr/tapestry
>>>>
>>>> Please note that it's still draft versions, don't worry about alignment
>>>> and positioning problem at the moment.
>>>>
>>>>
>>>> On Wed, May 26, 2010 at 6:46 PM, Thiago H. de Paula Figueiredo<
>>>> thiagohp@gmail.com> wrote:
>>>>
>>>> On Wed, 26 May 2010 12:27:31 -0300, Christophe Cordenier<
>>>>
>>>>> christophe.cordenier@gmail.com> wrote:
>>>>>
>>>>> As i am already a big fan of Robin's work, my opinion won't be much
>>>>>
>>>>> objective :)
>>>>>>
>>>>>> I have only one suggestion, A subtitle would be nice to express the
>>>>>> Tapestry philosophy. I have though to 'Compose your Web Application'
>>>>>>
>>>>>>
>>>>>> A slogan for Tapestry? Hum, nice idea! But I don't think 'Compose
>>>>> your
>>>>> Web
>>>>> Application' is good enough . . .
>>>>>
>>>>> This remembers something I read once: "Tapestry is what JSF should have
>>>>> been". :P
>>>>>
>>>>> Development is Art !
>>>>>
>>>>>
>>>>>>
>>>>>> I agree 1000%. That's why my little company is named Ars Machina (ars
>>>>> =
>>>>> art, machina = machine)
>>>>>
>>>>>
>>>>> --
>>>>> 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: dev-unsubscribe@tapestry.apache.org
>>>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>>>
>>>>>
>>>>>
>>>>>
>>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>
>>>
>>>
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
Re: [DISCUSS] Tapestry homepage redesign
Posted by Ulrich Stärk <ul...@spielviel.de>.
No they are not. In No. 2, 3 and 4 the green bar extends over the whole page width, and in 2 the
green backgroud image in the banner does as well.
Uli
On 27.05.2010 10:21, Robin Komiwes wrote:
> Yes Ulrich, you're right, there is something odd with the gradient and it
> should be replaced. I'll fix that when the new logo will be ready.
>
> Just to be sure, all layouts are fixed, it's just that there is no border
> anymore. I do prefer 3 and 4, but I can't make my choice between the classic
> version and the slider version.
>
> On Thu, May 27, 2010 at 9:29 AM, Ulrich Stärk<ul...@spielviel.de> wrote:
>
>> I still like No. 1 best. That's probably because of my preference for
>> fixed-width layouts. The content area is clearly delimited by the shadow
>> border, the key features are all visible at once and it's not obtrusive. The
>> banner might need some more tweaking, something feels odd about the green
>> background image, but I can't put a finger on it.
>>
>> Cheers,
>>
>> Uli
>>
>>
>> On 26.05.2010 18:58, Robin Komiwes wrote:
>>
>>> Fun :) On the first versions of Wooki, the title of the sample book when
>>> launching the application was :
>>> "Tapestry 5 : When development meets Art"
>>>
>>> http://github.com/robink/wooki/blob/7a3aaa0a9bd87856cab45fa1a012424423d9093d/src/main/java/com/wooki/services/StartupServiceImpl.java
>>>
>>>
>>> By the way, the first draft have moved.
>>> I'll now make new proposals by adding them into a subfolders
>>> Check http://komiwes.fr/tapestry
>>>
>>> Please note that it's still draft versions, don't worry about alignment
>>> and positioning problem at the moment.
>>>
>>>
>>> On Wed, May 26, 2010 at 6:46 PM, Thiago H. de Paula Figueiredo<
>>> thiagohp@gmail.com> wrote:
>>>
>>> On Wed, 26 May 2010 12:27:31 -0300, Christophe Cordenier<
>>>> christophe.cordenier@gmail.com> wrote:
>>>>
>>>> As i am already a big fan of Robin's work, my opinion won't be much
>>>>
>>>>> objective :)
>>>>>
>>>>> I have only one suggestion, A subtitle would be nice to express the
>>>>> Tapestry philosophy. I have though to 'Compose your Web Application'
>>>>>
>>>>>
>>>> A slogan for Tapestry? Hum, nice idea! But I don't think 'Compose your
>>>> Web
>>>> Application' is good enough . . .
>>>>
>>>> This remembers something I read once: "Tapestry is what JSF should have
>>>> been". :P
>>>>
>>>> Development is Art !
>>>>
>>>>>
>>>>>
>>>> I agree 1000%. That's why my little company is named Ars Machina (ars =
>>>> art, machina = machine)
>>>>
>>>>
>>>> --
>>>> 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: dev-unsubscribe@tapestry.apache.org
>>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>>
>>>>
>>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [DISCUSS] Tapestry homepage redesign
Posted by Robin Komiwes <ro...@gmail.com>.
Yes Ulrich, you're right, there is something odd with the gradient and it
should be replaced. I'll fix that when the new logo will be ready.
Just to be sure, all layouts are fixed, it's just that there is no border
anymore. I do prefer 3 and 4, but I can't make my choice between the classic
version and the slider version.
On Thu, May 27, 2010 at 9:29 AM, Ulrich Stärk <ul...@spielviel.de> wrote:
> I still like No. 1 best. That's probably because of my preference for
> fixed-width layouts. The content area is clearly delimited by the shadow
> border, the key features are all visible at once and it's not obtrusive. The
> banner might need some more tweaking, something feels odd about the green
> background image, but I can't put a finger on it.
>
> Cheers,
>
> Uli
>
>
> On 26.05.2010 18:58, Robin Komiwes wrote:
>
>> Fun :) On the first versions of Wooki, the title of the sample book when
>> launching the application was :
>> "Tapestry 5 : When development meets Art"
>>
>> http://github.com/robink/wooki/blob/7a3aaa0a9bd87856cab45fa1a012424423d9093d/src/main/java/com/wooki/services/StartupServiceImpl.java
>>
>>
>> By the way, the first draft have moved.
>> I'll now make new proposals by adding them into a subfolders
>> Check http://komiwes.fr/tapestry
>>
>> Please note that it's still draft versions, don't worry about alignment
>> and positioning problem at the moment.
>>
>>
>> On Wed, May 26, 2010 at 6:46 PM, Thiago H. de Paula Figueiredo<
>> thiagohp@gmail.com> wrote:
>>
>> On Wed, 26 May 2010 12:27:31 -0300, Christophe Cordenier<
>>> christophe.cordenier@gmail.com> wrote:
>>>
>>> As i am already a big fan of Robin's work, my opinion won't be much
>>>
>>>> objective :)
>>>>
>>>> I have only one suggestion, A subtitle would be nice to express the
>>>> Tapestry philosophy. I have though to 'Compose your Web Application'
>>>>
>>>>
>>> A slogan for Tapestry? Hum, nice idea! But I don't think 'Compose your
>>> Web
>>> Application' is good enough . . .
>>>
>>> This remembers something I read once: "Tapestry is what JSF should have
>>> been". :P
>>>
>>> Development is Art !
>>>
>>>>
>>>>
>>> I agree 1000%. That's why my little company is named Ars Machina (ars =
>>> art, machina = machine)
>>>
>>>
>>> --
>>> 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: dev-unsubscribe@tapestry.apache.org
>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>
>>>
>>>
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
Re: [DISCUSS] Tapestry homepage redesign
Posted by Geoff Callender <ge...@gmail.com>.
I agree with Uli for the reasons he mentions. The fact that you can see and take in the key points at a glance is a real drawcard. Time to replace the unicorn though?
Nice work Robin.
On 27/05/2010, at 5:29 PM, Ulrich Stärk wrote:
> I still like No. 1 best. That's probably because of my preference for fixed-width layouts. The content area is clearly delimited by the shadow border, the key features are all visible at once and it's not obtrusive. The banner might need some more tweaking, something feels odd about the green background image, but I can't put a finger on it.
>
> Cheers,
>
> Uli
>
> On 26.05.2010 18:58, Robin Komiwes wrote:
>> Fun :) On the first versions of Wooki, the title of the sample book when
>> launching the application was :
>> "Tapestry 5 : When development meets Art"
>> http://github.com/robink/wooki/blob/7a3aaa0a9bd87856cab45fa1a012424423d9093d/src/main/java/com/wooki/services/StartupServiceImpl.java
>>
>>
>> By the way, the first draft have moved.
>> I'll now make new proposals by adding them into a subfolders
>> Check http://komiwes.fr/tapestry
>>
>> Please note that it's still draft versions, don't worry about alignment
>> and positioning problem at the moment.
>>
>>
>> On Wed, May 26, 2010 at 6:46 PM, Thiago H. de Paula Figueiredo<
>> thiagohp@gmail.com> wrote:
>>
>>> On Wed, 26 May 2010 12:27:31 -0300, Christophe Cordenier<
>>> christophe.cordenier@gmail.com> wrote:
>>>
>>> As i am already a big fan of Robin's work, my opinion won't be much
>>>> objective :)
>>>>
>>>> I have only one suggestion, A subtitle would be nice to express the
>>>> Tapestry philosophy. I have though to 'Compose your Web Application'
>>>>
>>>
>>> A slogan for Tapestry? Hum, nice idea! But I don't think 'Compose your Web
>>> Application' is good enough . . .
>>>
>>> This remembers something I read once: "Tapestry is what JSF should have
>>> been". :P
>>>
>>> Development is Art !
>>>>
>>>
>>> I agree 1000%. That's why my little company is named Ars Machina (ars =
>>> art, machina = machine)
>>>
>>>
>>> --
>>> 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: dev-unsubscribe@tapestry.apache.org
>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>
>>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [DISCUSS] Tapestry homepage redesign
Posted by Ulrich Stärk <ul...@spielviel.de>.
I still like No. 1 best. That's probably because of my preference for fixed-width layouts. The
content area is clearly delimited by the shadow border, the key features are all visible at once and
it's not obtrusive. The banner might need some more tweaking, something feels odd about the green
background image, but I can't put a finger on it.
Cheers,
Uli
On 26.05.2010 18:58, Robin Komiwes wrote:
> Fun :) On the first versions of Wooki, the title of the sample book when
> launching the application was :
> "Tapestry 5 : When development meets Art"
> http://github.com/robink/wooki/blob/7a3aaa0a9bd87856cab45fa1a012424423d9093d/src/main/java/com/wooki/services/StartupServiceImpl.java
>
>
> By the way, the first draft have moved.
> I'll now make new proposals by adding them into a subfolders
> Check http://komiwes.fr/tapestry
>
> Please note that it's still draft versions, don't worry about alignment
> and positioning problem at the moment.
>
>
> On Wed, May 26, 2010 at 6:46 PM, Thiago H. de Paula Figueiredo<
> thiagohp@gmail.com> wrote:
>
>> On Wed, 26 May 2010 12:27:31 -0300, Christophe Cordenier<
>> christophe.cordenier@gmail.com> wrote:
>>
>> As i am already a big fan of Robin's work, my opinion won't be much
>>> objective :)
>>>
>>> I have only one suggestion, A subtitle would be nice to express the
>>> Tapestry philosophy. I have though to 'Compose your Web Application'
>>>
>>
>> A slogan for Tapestry? Hum, nice idea! But I don't think 'Compose your Web
>> Application' is good enough . . .
>>
>> This remembers something I read once: "Tapestry is what JSF should have
>> been". :P
>>
>> Development is Art !
>>>
>>
>> I agree 1000%. That's why my little company is named Ars Machina (ars =
>> art, machina = machine)
>>
>>
>> --
>> 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: dev-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [DISCUSS] Tapestry homepage redesign
Posted by Robin Komiwes <ro...@gmail.com>.
Fun :) On the first versions of Wooki, the title of the sample book when
launching the application was :
"Tapestry 5 : When development meets Art"
http://github.com/robink/wooki/blob/7a3aaa0a9bd87856cab45fa1a012424423d9093d/src/main/java/com/wooki/services/StartupServiceImpl.java
By the way, the first draft have moved.
I'll now make new proposals by adding them into a subfolders
Check http://komiwes.fr/tapestry
Please note that it's still draft versions, don't worry about alignment
and positioning problem at the moment.
On Wed, May 26, 2010 at 6:46 PM, Thiago H. de Paula Figueiredo <
thiagohp@gmail.com> wrote:
> On Wed, 26 May 2010 12:27:31 -0300, Christophe Cordenier <
> christophe.cordenier@gmail.com> wrote:
>
> As i am already a big fan of Robin's work, my opinion won't be much
>> objective :)
>>
>> I have only one suggestion, A subtitle would be nice to express the
>> Tapestry philosophy. I have though to 'Compose your Web Application'
>>
>
> A slogan for Tapestry? Hum, nice idea! But I don't think 'Compose your Web
> Application' is good enough . . .
>
> This remembers something I read once: "Tapestry is what JSF should have
> been". :P
>
> Development is Art !
>>
>
> I agree 1000%. That's why my little company is named Ars Machina (ars =
> art, machina = machine)
>
>
> --
> 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: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
Re: [DISCUSS] Tapestry homepage redesign
Posted by "Thiago H. de Paula Figueiredo" <th...@gmail.com>.
On Wed, 26 May 2010 12:27:31 -0300, Christophe Cordenier
<ch...@gmail.com> wrote:
> As i am already a big fan of Robin's work, my opinion won't be much
> objective :)
>
> I have only one suggestion, A subtitle would be nice to express the
> Tapestry philosophy. I have though to 'Compose your Web Application'
A slogan for Tapestry? Hum, nice idea! But I don't think 'Compose your Web
Application' is good enough . . .
This remembers something I read once: "Tapestry is what JSF should have
been". :P
> Development is Art !
I agree 1000%. That's why my little company is named Ars Machina (ars =
art, machina = machine)
--
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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [DISCUSS] Tapestry homepage redesign
Posted by Christophe Cordenier <ch...@gmail.com>.
Hi
2010/5/25 Robin Komiwes <ro...@gmail.com>
> I said some weeks ago that I will assist the documentation renew effort by
> proposing a redesign for Tapestry homepage.
>
> I'm quite satisfied with the first draft and I now need the community
> feedback to know if I should stop or continue this way. Of course, if
> someone wants to help on the content or the design, you are very welcome.
>
> The URLs :
> http://komiwes.fr/tapestry
> http://komiwes.fr/tapestry/getting_started.htm
> http://komiwes.fr/tapestry/community.htm
>
As i am already a big fan of Robin's work, my opinion won't be much
objective :)
I have only one suggestion, A subtitle would be nice to express the Tapestry
philosophy.
I have though to 'Compose your Web Application'
Compose ofcourse because it's a component oriented framework, but also
because Tapestry is elegant and sometime as a developer we feel like artists
or musicians... Just an idea :) Development is Art !
Anyway, this is really a nice work !
--
Regards,
Christophe Cordenier.
Developer of wooki @wookicentral.com
Re: [DISCUSS] Tapestry homepage redesign
Posted by Ulrich Stärk <ul...@spielviel.de>.
While I agree that a new design should be appealing to first-time users, we shouldn't neglect
returning users searching for specific pieces of information. I like the overall new design but I'd
put a little bit more emphasis on the links to documentation, downloads, javadocs, etc.
Great Job! I like it very much!
Uli
On 25.05.2010 12:06, Robin Komiwes wrote:
> I said some weeks ago that I will assist the documentation renew effort by
> proposing a redesign for Tapestry homepage.
>
> I'm quite satisfied with the first draft and I now need the community
> feedback to know if I should stop or continue this way. Of course, if
> someone wants to help on the content or the design, you are very welcome.
>
> The URLs :
> http://komiwes.fr/tapestry
> http://komiwes.fr/tapestry/getting_started.htm
> http://komiwes.fr/tapestry/community.htm
>
> Now, here are the key principles of this redesign. I've tried to follow
> them, and some may need to be expressed more.
>
> - Everything is marketing
> Others frameworks understand that well. They all have a shiny homepage, with
> key words, quotes from great people and baselines that you can't miss.
>
> The homepage should seduce and convince people. You've got to know that the
> framework you are using, or about to, is one of the best frameworks. In
> fact, there are plenty of good frameworks, if you launch tomorrow another
> "good framework", you are already dead. You need to offer a rockstar
> framework.
>
> On this redesign, a newcomer will be satisfied by how the information is
> clear and concise. He will know the concept of Tapestry (cf baseline) and
> will instantly have an idea of Tapestry strengths (cf Java power, scripting
> ease, highly productive).
>
> Finally he will be invited to give 20 minutes of its time to try the
> framework and realize how true was what we announced before.
>
> - Community
> Every framework should focus on its community. IMHO, that's another key
> point: again, if you think that an open source framework will buzz just
> because it is well made, you may have miss how the internet has evolved
> since some years. Ruby on Rails and jQuery have integrated that since the
> beginning. Focusing on the community is mandatory. Why?
>
> First, because as a Web framework developer, you can't cover every feature.
> Web is just too big. Especially in the Java ecosystem. If someone cover a
> feature for you, thanks him and then do advertising for its contribution as
> it was one of the features of the framework. It should be presented as a
> part of the framework itself, not as "a nice side project that you may look
> to if you want to...".
>
> Secondly, because the web is social. If people feels that they are part of
> an active community, they will be proud of it and will wants to make other
> people joining it. They will blog for you, they will evangelize for you. In
> fact, they will to the marketing job for you.
>
> I think the effort on this point should be pushed a lot further. We should
> have some specs on how to write and provide components library, how to
> provides plugins. We should have a place where to publish them.
>
> We should also have an open sourced keynote available to make presentations
> of Tapestry 5, like Howard's one :
> http://www.slideshare.net/hlship/tapestry-5-java-power-scripting-ease
> Everyone should be able to grab it and then do a presentation to its local
> JUG.
>
> - Fresh content
> It's important to look like active. We all know here that Tapestry is active
> but if you look at the actual website, there is no clue about that.
> Here, I think using a specific Twitter account (I've reserved @tapestry_5)
> for pushing news both on a social network and on the Tapestry website would
> be great. We would be able to easily push fresh, concise news from both
> Tapestry 5 framework and any other related tweets.
>
> - Efficiency
> One of the "cons" of maven sites is that they make you writing big pages and
> big menus. It is bad because it results in an insanely big amount of data
> that kills the data itself.
> The homepage should be efficient and concise.
>
> - References
> Real Tapestry applications showcase is a must have. We should be able to say
> "Hey, look! They've been using Tapestry in production and see how nice it
> works.". We already have some greats examples and we should show them.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [DISCUSS] Tapestry homepage redesign
Posted by Piero Sartini <li...@pierosartini.de>.
> I don't think we should use twitter to manage our news. Its true that
> twitter is important, but I think we need a master that is under our
> control.
> What do you think about using confluence and pushing the news to
> twitter, facebook and others automatically? This should be possible
> through the RSS functionality.
Another argument is that I can easily imagine news entries longer than
140 characters...
Piero
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [DISCUSS] Tapestry homepage redesign
Posted by Piero Sartini <li...@pierosartini.de>.
> Let's make a decision on this point, but I think we have to keep the menu
> line simple with only key items. In my humble opinion, sub menus or a two
> lines menu are too much :)
> If we really need to push others links, let's place them somewhere else,
> like under the main content, under the fresh news, or like JRuby does with a
> slider.
I think we will need a submenu - but I am with you that it should be
located somewhere in the main content area (and not in the top link
line).
> [Twitter & fresh content]
> Twitter is a must have. It's true that we could also use confluence for that
> but we've got to have a presence on Twitter. Every buzz start from this
> social network. By the way, there are RSS feeds for each twitter profile.
I don't think we should use twitter to manage our news. Its true that
twitter is important, but I think we need a master that is under our
control.
What do you think about using confluence and pushing the news to
twitter, facebook and others automatically? This should be possible
through the RSS functionality.
> I also first thought about using #tapestry5 hash tag but there is a problem
> with this approach: we don't have the control over what is said. What if
> someone tweet something like "#tapestry5 is too complicated!" ? With a
> custom twitter account, we can push a selection of tweets from other people
> by simply doing RT.
In my oppinion this is something we can't, and more important should
not control. If we want to build a healthy community, we can't start
to censor oppinions. But I guess this was related to using twitter as
news-engine...
My proposal: use confluence for managing news - but pesent a "latest
buzz" box at the start page as well (which includes everything postet
with #tap5 or #tapestry5 ).
> I see the same problem if we push last emails from the mailing list.
I really don't see this as a problem - tapestry is a community effort
and we should not be afraid of bad oppinions. Its better to have a few
bad headlines on the start page from time to time than don't have any
community stuff in place.
Piero
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [DISCUSS] Tapestry homepage redesign
Posted by "Thiago H. de Paula Figueiredo" <th...@gmail.com>.
On Wed, 26 May 2010 07:52:35 -0300, Robin Komiwes
<ro...@gmail.com> wrote:
> [Returning Users & menu]
> It seems that there are different thoughts on this.
> If we put too much links for things like Javadoc, component references
> etc., we may loose newcomers. I also like to have the control over
> visitors
> navigation. I believe that returning users will just bookmark the
> Documentation page. We could propose a pretty URL like :
> http://tapestry.apache.org/doc
I agree with Robin. Old users can just bookmark the documentation URL.
This one will have all the links we want
> [Twitter & fresh content]
> Twitter is a must have. It's true that we could also use confluence for
> that but we've got to have a presence on Twitter. Every buzz start from
> this
> social network. By the way, there are RSS feeds for each twitter profile.
Regarding showing RSS feed, I guess there are some good JavaScript
readers, so we can stick to static pages.
> I also first thought about using #tapestry5 hash tag but there is a
> problem with this approach: we don't have the control over what is said.
> What if
> someone tweet something like "#tapestry5 is too complicated!" ? With a
> custom twitter account, we can push a selection of tweets from other
> people by simply doing RT.
We could aggregate some RSS feeds (known Twitter accounts, known blogs)
and show it as a single RSS feed. I guess this isn't hard with Tapestry
and Rome.
--
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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [DISCUSS] Tapestry homepage redesign
Posted by Christian Edward Gruber <ch...@gmail.com>.
Sweet! Still trying to figure out the unicorn. Must have been a
discussion I missed. :)
Christian.
On May 26, 2010, at 12:31 PM, Massimo Lusetti wrote:
> On Wed, May 26, 2010 at 4:47 PM, Ulrich Stärk <ul...@spielviel.de>
> wrote:
>
>> I just migrated your design to our confluence space which gets
>> exported at
>> [1]. All the content is coming from the wiki already.
>>
>> Cheers,
>>
>> Uli
>>
>> [1] https://cwiki.apache.org/TAPESTRY/index.html
>>
>
> Yes very very nice!
>
> Cheers
> --
> Massimo
> http://meridio.blogspot.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [DISCUSS] Tapestry homepage redesign
Posted by Massimo Lusetti <ml...@gmail.com>.
On Wed, May 26, 2010 at 4:47 PM, Ulrich Stärk <ul...@spielviel.de> wrote:
> I just migrated your design to our confluence space which gets exported at
> [1]. All the content is coming from the wiki already.
>
> Cheers,
>
> Uli
>
> [1] https://cwiki.apache.org/TAPESTRY/index.html
>
Yes very very nice!
Cheers
--
Massimo
http://meridio.blogspot.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [DISCUSS] Tapestry homepage redesign
Posted by Ulrich Stärk <ul...@spielviel.de>.
I see. That will need some more tweaking then.
On 26.05.2010 17:11, Piero Sartini wrote:
>> I just migrated your design to our confluence space which gets exported at
>> [1]. All the content is coming from the wiki already.
>
> Great!
>
> How are the comments intended to work? I see two problems (but maybe
> its just that you did not make this work):
> - It seems as comments are exported together with the page and are not
> displayed in real-time. (my comment is not visible on the page)
> - It seems to be impossible to create a comment from the exported
> page. At least I was only able to create it within the wiki.
> (after clicking on the headline you come to a page with the news text only)
>
> Piero
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [DISCUSS] Tapestry homepage redesign
Posted by Piero Sartini <li...@pierosartini.de>.
> I just migrated your design to our confluence space which gets exported at
> [1]. All the content is coming from the wiki already.
Great!
How are the comments intended to work? I see two problems (but maybe
its just that you did not make this work):
- It seems as comments are exported together with the page and are not
displayed in real-time. (my comment is not visible on the page)
- It seems to be impossible to create a comment from the exported
page. At least I was only able to create it within the wiki.
(after clicking on the headline you come to a page with the news text only)
Piero
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [DISCUSS] Tapestry homepage redesign
Posted by Ulrich Stärk <ul...@spielviel.de>.
I just migrated your design to our confluence space which gets exported at [1]. All the content is
coming from the wiki already.
Cheers,
Uli
[1] https://cwiki.apache.org/TAPESTRY/index.html
On 26.05.2010 14:09, Ulrich Stärk wrote:
> Regarding the environment I guess we stick with confluence for the time
> being. Content is created in the wiki and gets exported to static html
> pages every hour. News items will be created in confluence as well and
> displayed somewhere on the website with an additional RSS feed for the
> news. Confluence also allows the inclusion of arbitrary RSS feeds (e.g.
> Twitter feeds via RSS) though that macro has been disabled lately. I'll
> talk to infrastructure about it. Or we just ship some javascript that
> includes the twitter content.
>
> Have you already signed a CLA? If not you might want to consider doing
> so, afterwards I can grant you access to confluence and you can help out
> there.
>
> Cheers,
>
> Uli
>
> On 26.05.2010 12:52, Robin Komiwes wrote:
>> Hi,
>>
>> Glad too see all theses replies. I'm convinced that something really good
>> can emerge from this.
>>
>> First, I just remind you all that it was just a "first draft". I'm
>> completely aware that the current version needs improvements. It was a
>> test
>> to see how the community would welcome that kind of proposal.
>>
>> I will integrate suggestions and will certainly publish the result on
>> Github. It will be easier to collaborate then.
>>
>> [Environment]
>> I don't have any clue about the constraints of Apache Foundation hosting.
>> Where could I get some info about that? Is it possible to run a Tapestry
>> instance? (to build a the community section)
>>
>> Actually it's pure HTML. We could push theses files in Tapestry project
>> sources and make them filtered by maven to replace some keywords (like
>> Tapestry version).
>>
>> By the way, yes, it'is a proposal for http://tapestry.apache.org
>>
>> [Returning Users& menu]
>> It seems that there are different thoughts on this.
>> If we put too much links for things like Javadoc, component references
>> etc.,
>> we may loose newcomers. I also like to have the control over visitors
>> navigation.
>> I believe that returning users will just bookmark the Documentation
>> page. We
>> could propose a pretty URL like : http://tapestry.apache.org/doc
>>
>> Let's make a decision on this point, but I think we have to keep the menu
>> line simple with only key items. In my humble opinion, sub menus or a two
>> lines menu are too much :)
>> If we really need to push others links, let's place them somewhere else,
>> like under the main content, under the fresh news, or like JRuby does
>> with a
>> slider.
>>
>> [Twitter& fresh content]
>> Twitter is a must have. It's true that we could also use confluence
>> for that
>> but we've got to have a presence on Twitter. Every buzz start from this
>> social network. By the way, there are RSS feeds for each twitter profile.
>>
>> I also first thought about using #tapestry5 hash tag but there is a
>> problem
>> with this approach: we don't have the control over what is said. What if
>> someone tweet something like "#tapestry5 is too complicated!" ? With a
>> custom twitter account, we can push a selection of tweets from other
>> people
>> by simply doing RT.
>>
>> I see the same problem if we push last emails from the mailing list.
>>
>>
>>
>> Anyway, this is a discussion, you have my point of view, but the
>> community
>> will have the final word! :)
>>
>> I would love to see the new home page release synced with the release of
>> Tapestry 5.2, what do you think about that?
>>
>>
>> On Wed, May 26, 2010 at 9:33 AM, Ulrich Stärk<ul...@spielviel.de> wrote:
>>
>>> It does. Check out [1].
>>>
>>> Uli
>>>
>>> [1] https://cwiki.apache.org/TAPESTRY/index.html
>>>
>>>
>>> On 25.05.2010 23:13, Ulrich Stärk wrote:
>>>
>>>> Oh and no problem to include news items added inside confluence to the
>>>> generated outputs (even with comments if wanted). I don't know whether
>>>> it supports RSS though, will have to check.
>>>>
>>>> On 25.05.2010 22:08, Ulrich Stärk wrote:
>>>>
>>>>> I'd configure confluence to auto-generate the contents with the new
>>>>> design included. Just a matter of some tweaking once we've settled
>>>>> for a
>>>>> design.
>>>>>
>>>>> Uli
>>>>>
>>>>> On 25.05.2010 18:48, Howard Lewis Ship wrote:
>>>>>
>>>>>> You are bringing tears to my eyes. This looks fantastic. I assume
>>>>>> this
>>>>>> is a replacement for http://tapestry.apache.org, right?
>>>>>>
>>>>>> Is this mock-up manually generated, or are you using some kind of
>>>>>> script? Ideally this would be easy to regenerate and redeploy live,
>>>>>> when changes occur. Also on the wish list, an RSS feed driven by a
>>>>>> "News" tab. Perhaps we need some main tabs across the top (the
>>>>>> current set) and some secondary tabs down the side (component
>>>>>> reference, older releases, news, etc.).
>>>>>>
>>>>>> As a side note ... Widen (one of my clients) has donated some
>>>>>> designer
>>>>>> time to work on the Tapestry logo, which could urgently use some
>>>>>> refreshing. We'll have a separate discussion to choose a new logo
>>>>>> design (or stick with the current one, I suppose).
>>>>>>
>>>>>> On Tue, May 25, 2010 at 9:31 AM, Jesse Kuhnert<jk...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Looks like a pretty good step in a new direction. Had a couple
>>>>>>> thoughts though:
>>>>>>>
>>>>>>> -) Something looks off on the tapestry word lettering of the banner
>>>>>>> logo. I think it's the white edge on green background but don't know
>>>>>>> what the graphic design fix should be.
>>>>>>> -) The center aligned text in the boxes up top doesn't look quite
>>>>>>> right either, should probably be left justified at least.
>>>>>>> -) Don't like the font for some reason, even if it is what is
>>>>>>> already
>>>>>>> used. How does helvetica look? =)
>>>>>>> -) The text boxes or the headers above them just below the banner
>>>>>>> logo
>>>>>>> should probably have links to something on the real site.
>>>>>>>
>>>>>>> Overall it does look like a great start though, just think it needs
>>>>>>> more polish and careful thought. Right now it looks good, but not
>>>>>>> professional.
>>>>>>>
>>>>>>> don't mean to sound negative, just being honest.
>>>>>>>
>>>>>>> On Tue, May 25, 2010 at 6:06 AM, Robin
>>>>>>> Komiwes<ro...@gmail.com> wrote:
>>>>>>>
>>>>>>>> I said some weeks ago that I will assist the documentation renew
>>>>>>>> effort by
>>>>>>>> proposing a redesign for Tapestry homepage.
>>>>>>>>
>>>>>>>> I'm quite satisfied with the first draft and I now need the
>>>>>>>> community
>>>>>>>> feedback to know if I should stop or continue this way. Of
>>>>>>>> course, if
>>>>>>>> someone wants to help on the content or the design, you are very
>>>>>>>> welcome.
>>>>>>>>
>>>>>>>> The URLs :
>>>>>>>> http://komiwes.fr/tapestry
>>>>>>>> http://komiwes.fr/tapestry/getting_started.htm
>>>>>>>> http://komiwes.fr/tapestry/community.htm
>>>>>>>>
>>>>>>>> Now, here are the key principles of this redesign. I've tried to
>>>>>>>> follow
>>>>>>>> them, and some may need to be expressed more.
>>>>>>>>
>>>>>>>> - Everything is marketing
>>>>>>>> Others frameworks understand that well. They all have a shiny
>>>>>>>> homepage, with
>>>>>>>> key words, quotes from great people and baselines that you can't
>>>>>>>> miss.
>>>>>>>>
>>>>>>>> The homepage should seduce and convince people. You've got to know
>>>>>>>> that the
>>>>>>>> framework you are using, or about to, is one of the best
>>>>>>>> frameworks. In
>>>>>>>> fact, there are plenty of good frameworks, if you launch tomorrow
>>>>>>>> another
>>>>>>>> "good framework", you are already dead. You need to offer a
>>>>>>>> rockstar
>>>>>>>> framework.
>>>>>>>>
>>>>>>>> On this redesign, a newcomer will be satisfied by how the
>>>>>>>> information is
>>>>>>>> clear and concise. He will know the concept of Tapestry (cf
>>>>>>>> baseline) and
>>>>>>>> will instantly have an idea of Tapestry strengths (cf Java power,
>>>>>>>> scripting
>>>>>>>> ease, highly productive).
>>>>>>>>
>>>>>>>> Finally he will be invited to give 20 minutes of its time to try
>>>>>>>> the
>>>>>>>> framework and realize how true was what we announced before.
>>>>>>>>
>>>>>>>> - Community
>>>>>>>> Every framework should focus on its community. IMHO, that's another
>>>>>>>> key
>>>>>>>> point: again, if you think that an open source framework will buzz
>>>>>>>> just
>>>>>>>> because it is well made, you may have miss how the internet has
>>>>>>>> evolved
>>>>>>>> since some years. Ruby on Rails and jQuery have integrated that
>>>>>>>> since the
>>>>>>>> beginning. Focusing on the community is mandatory. Why?
>>>>>>>>
>>>>>>>> First, because as a Web framework developer, you can't cover every
>>>>>>>> feature.
>>>>>>>> Web is just too big. Especially in the Java ecosystem. If someone
>>>>>>>> cover a
>>>>>>>> feature for you, thanks him and then do advertising for its
>>>>>>>> contribution as
>>>>>>>> it was one of the features of the framework. It should be presented
>>>>>>>> as a
>>>>>>>> part of the framework itself, not as "a nice side project that you
>>>>>>>> may look
>>>>>>>> to if you want to...".
>>>>>>>>
>>>>>>>> Secondly, because the web is social. If people feels that they are
>>>>>>>> part of
>>>>>>>> an active community, they will be proud of it and will wants to
>>>>>>>> make
>>>>>>>> other
>>>>>>>> people joining it. They will blog for you, they will evangelize for
>>>>>>>> you. In
>>>>>>>> fact, they will to the marketing job for you.
>>>>>>>>
>>>>>>>> I think the effort on this point should be pushed a lot further. We
>>>>>>>> should
>>>>>>>> have some specs on how to write and provide components library,
>>>>>>>> how to
>>>>>>>> provides plugins. We should have a place where to publish them.
>>>>>>>>
>>>>>>>> We should also have an open sourced keynote available to make
>>>>>>>> presentations
>>>>>>>> of Tapestry 5, like Howard's one :
>>>>>>>> http://www.slideshare.net/hlship/tapestry-5-java-power-scripting-ease
>>>>>>>>
>>>>>>>> Everyone should be able to grab it and then do a presentation to
>>>>>>>> its
>>>>>>>> local
>>>>>>>> JUG.
>>>>>>>>
>>>>>>>> - Fresh content
>>>>>>>> It's important to look like active. We all know here that Tapestry
>>>>>>>> is active
>>>>>>>> but if you look at the actual website, there is no clue about that.
>>>>>>>> Here, I think using a specific Twitter account (I've reserved
>>>>>>>> @tapestry_5)
>>>>>>>> for pushing news both on a social network and on the Tapestry
>>>>>>>> website would
>>>>>>>> be great. We would be able to easily push fresh, concise news from
>>>>>>>> both
>>>>>>>> Tapestry 5 framework and any other related tweets.
>>>>>>>>
>>>>>>>> - Efficiency
>>>>>>>> One of the "cons" of maven sites is that they make you writing big
>>>>>>>> pages and
>>>>>>>> big menus. It is bad because it results in an insanely big
>>>>>>>> amount of
>>>>>>>> data
>>>>>>>> that kills the data itself.
>>>>>>>> The homepage should be efficient and concise.
>>>>>>>>
>>>>>>>> - References
>>>>>>>> Real Tapestry applications showcase is a must have. We should be
>>>>>>>> able to say
>>>>>>>> "Hey, look! They've been using Tapestry in production and see how
>>>>>>>> nice it
>>>>>>>> works.". We already have some greats examples and we should show
>>>>>>>> them.
>>>>>>>>
>>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>>
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>>>>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>>>
>>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>>
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>
>>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [DISCUSS] Tapestry homepage redesign
Posted by Ulrich Stärk <ul...@spielviel.de>.
Regarding the environment I guess we stick with confluence for the time being. Content is created in
the wiki and gets exported to static html pages every hour. News items will be created in confluence
as well and displayed somewhere on the website with an additional RSS feed for the news. Confluence
also allows the inclusion of arbitrary RSS feeds (e.g. Twitter feeds via RSS) though that macro has
been disabled lately. I'll talk to infrastructure about it. Or we just ship some javascript that
includes the twitter content.
Have you already signed a CLA? If not you might want to consider doing so, afterwards I can grant
you access to confluence and you can help out there.
Cheers,
Uli
On 26.05.2010 12:52, Robin Komiwes wrote:
> Hi,
>
> Glad too see all theses replies. I'm convinced that something really good
> can emerge from this.
>
> First, I just remind you all that it was just a "first draft". I'm
> completely aware that the current version needs improvements. It was a test
> to see how the community would welcome that kind of proposal.
>
> I will integrate suggestions and will certainly publish the result on
> Github. It will be easier to collaborate then.
>
> [Environment]
> I don't have any clue about the constraints of Apache Foundation hosting.
> Where could I get some info about that? Is it possible to run a Tapestry
> instance? (to build a the community section)
>
> Actually it's pure HTML. We could push theses files in Tapestry project
> sources and make them filtered by maven to replace some keywords (like
> Tapestry version).
>
> By the way, yes, it'is a proposal for http://tapestry.apache.org
>
> [Returning Users& menu]
> It seems that there are different thoughts on this.
> If we put too much links for things like Javadoc, component references etc.,
> we may loose newcomers. I also like to have the control over visitors
> navigation.
> I believe that returning users will just bookmark the Documentation page. We
> could propose a pretty URL like : http://tapestry.apache.org/doc
>
> Let's make a decision on this point, but I think we have to keep the menu
> line simple with only key items. In my humble opinion, sub menus or a two
> lines menu are too much :)
> If we really need to push others links, let's place them somewhere else,
> like under the main content, under the fresh news, or like JRuby does with a
> slider.
>
> [Twitter& fresh content]
> Twitter is a must have. It's true that we could also use confluence for that
> but we've got to have a presence on Twitter. Every buzz start from this
> social network. By the way, there are RSS feeds for each twitter profile.
>
> I also first thought about using #tapestry5 hash tag but there is a problem
> with this approach: we don't have the control over what is said. What if
> someone tweet something like "#tapestry5 is too complicated!" ? With a
> custom twitter account, we can push a selection of tweets from other people
> by simply doing RT.
>
> I see the same problem if we push last emails from the mailing list.
>
>
>
> Anyway, this is a discussion, you have my point of view, but the community
> will have the final word! :)
>
> I would love to see the new home page release synced with the release of
> Tapestry 5.2, what do you think about that?
>
>
> On Wed, May 26, 2010 at 9:33 AM, Ulrich Stärk<ul...@spielviel.de> wrote:
>
>> It does. Check out [1].
>>
>> Uli
>>
>> [1] https://cwiki.apache.org/TAPESTRY/index.html
>>
>>
>> On 25.05.2010 23:13, Ulrich Stärk wrote:
>>
>>> Oh and no problem to include news items added inside confluence to the
>>> generated outputs (even with comments if wanted). I don't know whether
>>> it supports RSS though, will have to check.
>>>
>>> On 25.05.2010 22:08, Ulrich Stärk wrote:
>>>
>>>> I'd configure confluence to auto-generate the contents with the new
>>>> design included. Just a matter of some tweaking once we've settled for a
>>>> design.
>>>>
>>>> Uli
>>>>
>>>> On 25.05.2010 18:48, Howard Lewis Ship wrote:
>>>>
>>>>> You are bringing tears to my eyes. This looks fantastic. I assume this
>>>>> is a replacement for http://tapestry.apache.org, right?
>>>>>
>>>>> Is this mock-up manually generated, or are you using some kind of
>>>>> script? Ideally this would be easy to regenerate and redeploy live,
>>>>> when changes occur. Also on the wish list, an RSS feed driven by a
>>>>> "News" tab. Perhaps we need some main tabs across the top (the
>>>>> current set) and some secondary tabs down the side (component
>>>>> reference, older releases, news, etc.).
>>>>>
>>>>> As a side note ... Widen (one of my clients) has donated some designer
>>>>> time to work on the Tapestry logo, which could urgently use some
>>>>> refreshing. We'll have a separate discussion to choose a new logo
>>>>> design (or stick with the current one, I suppose).
>>>>>
>>>>> On Tue, May 25, 2010 at 9:31 AM, Jesse Kuhnert<jk...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Looks like a pretty good step in a new direction. Had a couple
>>>>>> thoughts though:
>>>>>>
>>>>>> -) Something looks off on the tapestry word lettering of the banner
>>>>>> logo. I think it's the white edge on green background but don't know
>>>>>> what the graphic design fix should be.
>>>>>> -) The center aligned text in the boxes up top doesn't look quite
>>>>>> right either, should probably be left justified at least.
>>>>>> -) Don't like the font for some reason, even if it is what is already
>>>>>> used. How does helvetica look? =)
>>>>>> -) The text boxes or the headers above them just below the banner logo
>>>>>> should probably have links to something on the real site.
>>>>>>
>>>>>> Overall it does look like a great start though, just think it needs
>>>>>> more polish and careful thought. Right now it looks good, but not
>>>>>> professional.
>>>>>>
>>>>>> don't mean to sound negative, just being honest.
>>>>>>
>>>>>> On Tue, May 25, 2010 at 6:06 AM, Robin
>>>>>> Komiwes<ro...@gmail.com> wrote:
>>>>>>
>>>>>>> I said some weeks ago that I will assist the documentation renew
>>>>>>> effort by
>>>>>>> proposing a redesign for Tapestry homepage.
>>>>>>>
>>>>>>> I'm quite satisfied with the first draft and I now need the community
>>>>>>> feedback to know if I should stop or continue this way. Of course, if
>>>>>>> someone wants to help on the content or the design, you are very
>>>>>>> welcome.
>>>>>>>
>>>>>>> The URLs :
>>>>>>> http://komiwes.fr/tapestry
>>>>>>> http://komiwes.fr/tapestry/getting_started.htm
>>>>>>> http://komiwes.fr/tapestry/community.htm
>>>>>>>
>>>>>>> Now, here are the key principles of this redesign. I've tried to
>>>>>>> follow
>>>>>>> them, and some may need to be expressed more.
>>>>>>>
>>>>>>> - Everything is marketing
>>>>>>> Others frameworks understand that well. They all have a shiny
>>>>>>> homepage, with
>>>>>>> key words, quotes from great people and baselines that you can't miss.
>>>>>>>
>>>>>>> The homepage should seduce and convince people. You've got to know
>>>>>>> that the
>>>>>>> framework you are using, or about to, is one of the best
>>>>>>> frameworks. In
>>>>>>> fact, there are plenty of good frameworks, if you launch tomorrow
>>>>>>> another
>>>>>>> "good framework", you are already dead. You need to offer a rockstar
>>>>>>> framework.
>>>>>>>
>>>>>>> On this redesign, a newcomer will be satisfied by how the
>>>>>>> information is
>>>>>>> clear and concise. He will know the concept of Tapestry (cf
>>>>>>> baseline) and
>>>>>>> will instantly have an idea of Tapestry strengths (cf Java power,
>>>>>>> scripting
>>>>>>> ease, highly productive).
>>>>>>>
>>>>>>> Finally he will be invited to give 20 minutes of its time to try the
>>>>>>> framework and realize how true was what we announced before.
>>>>>>>
>>>>>>> - Community
>>>>>>> Every framework should focus on its community. IMHO, that's another
>>>>>>> key
>>>>>>> point: again, if you think that an open source framework will buzz
>>>>>>> just
>>>>>>> because it is well made, you may have miss how the internet has
>>>>>>> evolved
>>>>>>> since some years. Ruby on Rails and jQuery have integrated that
>>>>>>> since the
>>>>>>> beginning. Focusing on the community is mandatory. Why?
>>>>>>>
>>>>>>> First, because as a Web framework developer, you can't cover every
>>>>>>> feature.
>>>>>>> Web is just too big. Especially in the Java ecosystem. If someone
>>>>>>> cover a
>>>>>>> feature for you, thanks him and then do advertising for its
>>>>>>> contribution as
>>>>>>> it was one of the features of the framework. It should be presented
>>>>>>> as a
>>>>>>> part of the framework itself, not as "a nice side project that you
>>>>>>> may look
>>>>>>> to if you want to...".
>>>>>>>
>>>>>>> Secondly, because the web is social. If people feels that they are
>>>>>>> part of
>>>>>>> an active community, they will be proud of it and will wants to make
>>>>>>> other
>>>>>>> people joining it. They will blog for you, they will evangelize for
>>>>>>> you. In
>>>>>>> fact, they will to the marketing job for you.
>>>>>>>
>>>>>>> I think the effort on this point should be pushed a lot further. We
>>>>>>> should
>>>>>>> have some specs on how to write and provide components library, how to
>>>>>>> provides plugins. We should have a place where to publish them.
>>>>>>>
>>>>>>> We should also have an open sourced keynote available to make
>>>>>>> presentations
>>>>>>> of Tapestry 5, like Howard's one :
>>>>>>> http://www.slideshare.net/hlship/tapestry-5-java-power-scripting-ease
>>>>>>> Everyone should be able to grab it and then do a presentation to its
>>>>>>> local
>>>>>>> JUG.
>>>>>>>
>>>>>>> - Fresh content
>>>>>>> It's important to look like active. We all know here that Tapestry
>>>>>>> is active
>>>>>>> but if you look at the actual website, there is no clue about that.
>>>>>>> Here, I think using a specific Twitter account (I've reserved
>>>>>>> @tapestry_5)
>>>>>>> for pushing news both on a social network and on the Tapestry
>>>>>>> website would
>>>>>>> be great. We would be able to easily push fresh, concise news from
>>>>>>> both
>>>>>>> Tapestry 5 framework and any other related tweets.
>>>>>>>
>>>>>>> - Efficiency
>>>>>>> One of the "cons" of maven sites is that they make you writing big
>>>>>>> pages and
>>>>>>> big menus. It is bad because it results in an insanely big amount of
>>>>>>> data
>>>>>>> that kills the data itself.
>>>>>>> The homepage should be efficient and concise.
>>>>>>>
>>>>>>> - References
>>>>>>> Real Tapestry applications showcase is a must have. We should be
>>>>>>> able to say
>>>>>>> "Hey, look! They've been using Tapestry in production and see how
>>>>>>> nice it
>>>>>>> works.". We already have some greats examples and we should show them.
>>>>>>>
>>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>>>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>>
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [DISCUSS] Tapestry homepage redesign
Posted by Robin Komiwes <ro...@gmail.com>.
Hi,
Glad too see all theses replies. I'm convinced that something really good
can emerge from this.
First, I just remind you all that it was just a "first draft". I'm
completely aware that the current version needs improvements. It was a test
to see how the community would welcome that kind of proposal.
I will integrate suggestions and will certainly publish the result on
Github. It will be easier to collaborate then.
[Environment]
I don't have any clue about the constraints of Apache Foundation hosting.
Where could I get some info about that? Is it possible to run a Tapestry
instance? (to build a the community section)
Actually it's pure HTML. We could push theses files in Tapestry project
sources and make them filtered by maven to replace some keywords (like
Tapestry version).
By the way, yes, it'is a proposal for http://tapestry.apache.org
[Returning Users & menu]
It seems that there are different thoughts on this.
If we put too much links for things like Javadoc, component references etc.,
we may loose newcomers. I also like to have the control over visitors
navigation.
I believe that returning users will just bookmark the Documentation page. We
could propose a pretty URL like : http://tapestry.apache.org/doc
Let's make a decision on this point, but I think we have to keep the menu
line simple with only key items. In my humble opinion, sub menus or a two
lines menu are too much :)
If we really need to push others links, let's place them somewhere else,
like under the main content, under the fresh news, or like JRuby does with a
slider.
[Twitter & fresh content]
Twitter is a must have. It's true that we could also use confluence for that
but we've got to have a presence on Twitter. Every buzz start from this
social network. By the way, there are RSS feeds for each twitter profile.
I also first thought about using #tapestry5 hash tag but there is a problem
with this approach: we don't have the control over what is said. What if
someone tweet something like "#tapestry5 is too complicated!" ? With a
custom twitter account, we can push a selection of tweets from other people
by simply doing RT.
I see the same problem if we push last emails from the mailing list.
Anyway, this is a discussion, you have my point of view, but the community
will have the final word! :)
I would love to see the new home page release synced with the release of
Tapestry 5.2, what do you think about that?
On Wed, May 26, 2010 at 9:33 AM, Ulrich Stärk <ul...@spielviel.de> wrote:
> It does. Check out [1].
>
> Uli
>
> [1] https://cwiki.apache.org/TAPESTRY/index.html
>
>
> On 25.05.2010 23:13, Ulrich Stärk wrote:
>
>> Oh and no problem to include news items added inside confluence to the
>> generated outputs (even with comments if wanted). I don't know whether
>> it supports RSS though, will have to check.
>>
>> On 25.05.2010 22:08, Ulrich Stärk wrote:
>>
>>> I'd configure confluence to auto-generate the contents with the new
>>> design included. Just a matter of some tweaking once we've settled for a
>>> design.
>>>
>>> Uli
>>>
>>> On 25.05.2010 18:48, Howard Lewis Ship wrote:
>>>
>>>> You are bringing tears to my eyes. This looks fantastic. I assume this
>>>> is a replacement for http://tapestry.apache.org, right?
>>>>
>>>> Is this mock-up manually generated, or are you using some kind of
>>>> script? Ideally this would be easy to regenerate and redeploy live,
>>>> when changes occur. Also on the wish list, an RSS feed driven by a
>>>> "News" tab. Perhaps we need some main tabs across the top (the
>>>> current set) and some secondary tabs down the side (component
>>>> reference, older releases, news, etc.).
>>>>
>>>> As a side note ... Widen (one of my clients) has donated some designer
>>>> time to work on the Tapestry logo, which could urgently use some
>>>> refreshing. We'll have a separate discussion to choose a new logo
>>>> design (or stick with the current one, I suppose).
>>>>
>>>> On Tue, May 25, 2010 at 9:31 AM, Jesse Kuhnert<jk...@gmail.com>
>>>> wrote:
>>>>
>>>>> Looks like a pretty good step in a new direction. Had a couple
>>>>> thoughts though:
>>>>>
>>>>> -) Something looks off on the tapestry word lettering of the banner
>>>>> logo. I think it's the white edge on green background but don't know
>>>>> what the graphic design fix should be.
>>>>> -) The center aligned text in the boxes up top doesn't look quite
>>>>> right either, should probably be left justified at least.
>>>>> -) Don't like the font for some reason, even if it is what is already
>>>>> used. How does helvetica look? =)
>>>>> -) The text boxes or the headers above them just below the banner logo
>>>>> should probably have links to something on the real site.
>>>>>
>>>>> Overall it does look like a great start though, just think it needs
>>>>> more polish and careful thought. Right now it looks good, but not
>>>>> professional.
>>>>>
>>>>> don't mean to sound negative, just being honest.
>>>>>
>>>>> On Tue, May 25, 2010 at 6:06 AM, Robin
>>>>> Komiwes<ro...@gmail.com> wrote:
>>>>>
>>>>>> I said some weeks ago that I will assist the documentation renew
>>>>>> effort by
>>>>>> proposing a redesign for Tapestry homepage.
>>>>>>
>>>>>> I'm quite satisfied with the first draft and I now need the community
>>>>>> feedback to know if I should stop or continue this way. Of course, if
>>>>>> someone wants to help on the content or the design, you are very
>>>>>> welcome.
>>>>>>
>>>>>> The URLs :
>>>>>> http://komiwes.fr/tapestry
>>>>>> http://komiwes.fr/tapestry/getting_started.htm
>>>>>> http://komiwes.fr/tapestry/community.htm
>>>>>>
>>>>>> Now, here are the key principles of this redesign. I've tried to
>>>>>> follow
>>>>>> them, and some may need to be expressed more.
>>>>>>
>>>>>> - Everything is marketing
>>>>>> Others frameworks understand that well. They all have a shiny
>>>>>> homepage, with
>>>>>> key words, quotes from great people and baselines that you can't miss.
>>>>>>
>>>>>> The homepage should seduce and convince people. You've got to know
>>>>>> that the
>>>>>> framework you are using, or about to, is one of the best
>>>>>> frameworks. In
>>>>>> fact, there are plenty of good frameworks, if you launch tomorrow
>>>>>> another
>>>>>> "good framework", you are already dead. You need to offer a rockstar
>>>>>> framework.
>>>>>>
>>>>>> On this redesign, a newcomer will be satisfied by how the
>>>>>> information is
>>>>>> clear and concise. He will know the concept of Tapestry (cf
>>>>>> baseline) and
>>>>>> will instantly have an idea of Tapestry strengths (cf Java power,
>>>>>> scripting
>>>>>> ease, highly productive).
>>>>>>
>>>>>> Finally he will be invited to give 20 minutes of its time to try the
>>>>>> framework and realize how true was what we announced before.
>>>>>>
>>>>>> - Community
>>>>>> Every framework should focus on its community. IMHO, that's another
>>>>>> key
>>>>>> point: again, if you think that an open source framework will buzz
>>>>>> just
>>>>>> because it is well made, you may have miss how the internet has
>>>>>> evolved
>>>>>> since some years. Ruby on Rails and jQuery have integrated that
>>>>>> since the
>>>>>> beginning. Focusing on the community is mandatory. Why?
>>>>>>
>>>>>> First, because as a Web framework developer, you can't cover every
>>>>>> feature.
>>>>>> Web is just too big. Especially in the Java ecosystem. If someone
>>>>>> cover a
>>>>>> feature for you, thanks him and then do advertising for its
>>>>>> contribution as
>>>>>> it was one of the features of the framework. It should be presented
>>>>>> as a
>>>>>> part of the framework itself, not as "a nice side project that you
>>>>>> may look
>>>>>> to if you want to...".
>>>>>>
>>>>>> Secondly, because the web is social. If people feels that they are
>>>>>> part of
>>>>>> an active community, they will be proud of it and will wants to make
>>>>>> other
>>>>>> people joining it. They will blog for you, they will evangelize for
>>>>>> you. In
>>>>>> fact, they will to the marketing job for you.
>>>>>>
>>>>>> I think the effort on this point should be pushed a lot further. We
>>>>>> should
>>>>>> have some specs on how to write and provide components library, how to
>>>>>> provides plugins. We should have a place where to publish them.
>>>>>>
>>>>>> We should also have an open sourced keynote available to make
>>>>>> presentations
>>>>>> of Tapestry 5, like Howard's one :
>>>>>> http://www.slideshare.net/hlship/tapestry-5-java-power-scripting-ease
>>>>>> Everyone should be able to grab it and then do a presentation to its
>>>>>> local
>>>>>> JUG.
>>>>>>
>>>>>> - Fresh content
>>>>>> It's important to look like active. We all know here that Tapestry
>>>>>> is active
>>>>>> but if you look at the actual website, there is no clue about that.
>>>>>> Here, I think using a specific Twitter account (I've reserved
>>>>>> @tapestry_5)
>>>>>> for pushing news both on a social network and on the Tapestry
>>>>>> website would
>>>>>> be great. We would be able to easily push fresh, concise news from
>>>>>> both
>>>>>> Tapestry 5 framework and any other related tweets.
>>>>>>
>>>>>> - Efficiency
>>>>>> One of the "cons" of maven sites is that they make you writing big
>>>>>> pages and
>>>>>> big menus. It is bad because it results in an insanely big amount of
>>>>>> data
>>>>>> that kills the data itself.
>>>>>> The homepage should be efficient and concise.
>>>>>>
>>>>>> - References
>>>>>> Real Tapestry applications showcase is a must have. We should be
>>>>>> able to say
>>>>>> "Hey, look! They've been using Tapestry in production and see how
>>>>>> nice it
>>>>>> works.". We already have some greats examples and we should show them.
>>>>>>
>>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
Re: [DISCUSS] Tapestry homepage redesign
Posted by Ulrich Stärk <ul...@spielviel.de>.
It does. Check out [1].
Uli
[1] https://cwiki.apache.org/TAPESTRY/index.html
On 25.05.2010 23:13, Ulrich Stärk wrote:
> Oh and no problem to include news items added inside confluence to the
> generated outputs (even with comments if wanted). I don't know whether
> it supports RSS though, will have to check.
>
> On 25.05.2010 22:08, Ulrich Stärk wrote:
>> I'd configure confluence to auto-generate the contents with the new
>> design included. Just a matter of some tweaking once we've settled for a
>> design.
>>
>> Uli
>>
>> On 25.05.2010 18:48, Howard Lewis Ship wrote:
>>> You are bringing tears to my eyes. This looks fantastic. I assume this
>>> is a replacement for http://tapestry.apache.org, right?
>>>
>>> Is this mock-up manually generated, or are you using some kind of
>>> script? Ideally this would be easy to regenerate and redeploy live,
>>> when changes occur. Also on the wish list, an RSS feed driven by a
>>> "News" tab. Perhaps we need some main tabs across the top (the
>>> current set) and some secondary tabs down the side (component
>>> reference, older releases, news, etc.).
>>>
>>> As a side note ... Widen (one of my clients) has donated some designer
>>> time to work on the Tapestry logo, which could urgently use some
>>> refreshing. We'll have a separate discussion to choose a new logo
>>> design (or stick with the current one, I suppose).
>>>
>>> On Tue, May 25, 2010 at 9:31 AM, Jesse Kuhnert<jk...@gmail.com>
>>> wrote:
>>>> Looks like a pretty good step in a new direction. Had a couple
>>>> thoughts though:
>>>>
>>>> -) Something looks off on the tapestry word lettering of the banner
>>>> logo. I think it's the white edge on green background but don't know
>>>> what the graphic design fix should be.
>>>> -) The center aligned text in the boxes up top doesn't look quite
>>>> right either, should probably be left justified at least.
>>>> -) Don't like the font for some reason, even if it is what is already
>>>> used. How does helvetica look? =)
>>>> -) The text boxes or the headers above them just below the banner logo
>>>> should probably have links to something on the real site.
>>>>
>>>> Overall it does look like a great start though, just think it needs
>>>> more polish and careful thought. Right now it looks good, but not
>>>> professional.
>>>>
>>>> don't mean to sound negative, just being honest.
>>>>
>>>> On Tue, May 25, 2010 at 6:06 AM, Robin
>>>> Komiwes<ro...@gmail.com> wrote:
>>>>> I said some weeks ago that I will assist the documentation renew
>>>>> effort by
>>>>> proposing a redesign for Tapestry homepage.
>>>>>
>>>>> I'm quite satisfied with the first draft and I now need the community
>>>>> feedback to know if I should stop or continue this way. Of course, if
>>>>> someone wants to help on the content or the design, you are very
>>>>> welcome.
>>>>>
>>>>> The URLs :
>>>>> http://komiwes.fr/tapestry
>>>>> http://komiwes.fr/tapestry/getting_started.htm
>>>>> http://komiwes.fr/tapestry/community.htm
>>>>>
>>>>> Now, here are the key principles of this redesign. I've tried to
>>>>> follow
>>>>> them, and some may need to be expressed more.
>>>>>
>>>>> - Everything is marketing
>>>>> Others frameworks understand that well. They all have a shiny
>>>>> homepage, with
>>>>> key words, quotes from great people and baselines that you can't miss.
>>>>>
>>>>> The homepage should seduce and convince people. You've got to know
>>>>> that the
>>>>> framework you are using, or about to, is one of the best
>>>>> frameworks. In
>>>>> fact, there are plenty of good frameworks, if you launch tomorrow
>>>>> another
>>>>> "good framework", you are already dead. You need to offer a rockstar
>>>>> framework.
>>>>>
>>>>> On this redesign, a newcomer will be satisfied by how the
>>>>> information is
>>>>> clear and concise. He will know the concept of Tapestry (cf
>>>>> baseline) and
>>>>> will instantly have an idea of Tapestry strengths (cf Java power,
>>>>> scripting
>>>>> ease, highly productive).
>>>>>
>>>>> Finally he will be invited to give 20 minutes of its time to try the
>>>>> framework and realize how true was what we announced before.
>>>>>
>>>>> - Community
>>>>> Every framework should focus on its community. IMHO, that's another
>>>>> key
>>>>> point: again, if you think that an open source framework will buzz
>>>>> just
>>>>> because it is well made, you may have miss how the internet has
>>>>> evolved
>>>>> since some years. Ruby on Rails and jQuery have integrated that
>>>>> since the
>>>>> beginning. Focusing on the community is mandatory. Why?
>>>>>
>>>>> First, because as a Web framework developer, you can't cover every
>>>>> feature.
>>>>> Web is just too big. Especially in the Java ecosystem. If someone
>>>>> cover a
>>>>> feature for you, thanks him and then do advertising for its
>>>>> contribution as
>>>>> it was one of the features of the framework. It should be presented
>>>>> as a
>>>>> part of the framework itself, not as "a nice side project that you
>>>>> may look
>>>>> to if you want to...".
>>>>>
>>>>> Secondly, because the web is social. If people feels that they are
>>>>> part of
>>>>> an active community, they will be proud of it and will wants to make
>>>>> other
>>>>> people joining it. They will blog for you, they will evangelize for
>>>>> you. In
>>>>> fact, they will to the marketing job for you.
>>>>>
>>>>> I think the effort on this point should be pushed a lot further. We
>>>>> should
>>>>> have some specs on how to write and provide components library, how to
>>>>> provides plugins. We should have a place where to publish them.
>>>>>
>>>>> We should also have an open sourced keynote available to make
>>>>> presentations
>>>>> of Tapestry 5, like Howard's one :
>>>>> http://www.slideshare.net/hlship/tapestry-5-java-power-scripting-ease
>>>>> Everyone should be able to grab it and then do a presentation to its
>>>>> local
>>>>> JUG.
>>>>>
>>>>> - Fresh content
>>>>> It's important to look like active. We all know here that Tapestry
>>>>> is active
>>>>> but if you look at the actual website, there is no clue about that.
>>>>> Here, I think using a specific Twitter account (I've reserved
>>>>> @tapestry_5)
>>>>> for pushing news both on a social network and on the Tapestry
>>>>> website would
>>>>> be great. We would be able to easily push fresh, concise news from
>>>>> both
>>>>> Tapestry 5 framework and any other related tweets.
>>>>>
>>>>> - Efficiency
>>>>> One of the "cons" of maven sites is that they make you writing big
>>>>> pages and
>>>>> big menus. It is bad because it results in an insanely big amount of
>>>>> data
>>>>> that kills the data itself.
>>>>> The homepage should be efficient and concise.
>>>>>
>>>>> - References
>>>>> Real Tapestry applications showcase is a must have. We should be
>>>>> able to say
>>>>> "Hey, look! They've been using Tapestry in production and see how
>>>>> nice it
>>>>> works.". We already have some greats examples and we should show them.
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>>
>>>>
>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [DISCUSS] Tapestry homepage redesign
Posted by Ulrich Stärk <ul...@spielviel.de>.
Oh and no problem to include news items added inside confluence to the generated outputs (even with
comments if wanted). I don't know whether it supports RSS though, will have to check.
On 25.05.2010 22:08, Ulrich Stärk wrote:
> I'd configure confluence to auto-generate the contents with the new
> design included. Just a matter of some tweaking once we've settled for a
> design.
>
> Uli
>
> On 25.05.2010 18:48, Howard Lewis Ship wrote:
>> You are bringing tears to my eyes. This looks fantastic. I assume this
>> is a replacement for http://tapestry.apache.org, right?
>>
>> Is this mock-up manually generated, or are you using some kind of
>> script? Ideally this would be easy to regenerate and redeploy live,
>> when changes occur. Also on the wish list, an RSS feed driven by a
>> "News" tab. Perhaps we need some main tabs across the top (the
>> current set) and some secondary tabs down the side (component
>> reference, older releases, news, etc.).
>>
>> As a side note ... Widen (one of my clients) has donated some designer
>> time to work on the Tapestry logo, which could urgently use some
>> refreshing. We'll have a separate discussion to choose a new logo
>> design (or stick with the current one, I suppose).
>>
>> On Tue, May 25, 2010 at 9:31 AM, Jesse Kuhnert<jk...@gmail.com> wrote:
>>> Looks like a pretty good step in a new direction. Had a couple
>>> thoughts though:
>>>
>>> -) Something looks off on the tapestry word lettering of the banner
>>> logo. I think it's the white edge on green background but don't know
>>> what the graphic design fix should be.
>>> -) The center aligned text in the boxes up top doesn't look quite
>>> right either, should probably be left justified at least.
>>> -) Don't like the font for some reason, even if it is what is already
>>> used. How does helvetica look? =)
>>> -) The text boxes or the headers above them just below the banner logo
>>> should probably have links to something on the real site.
>>>
>>> Overall it does look like a great start though, just think it needs
>>> more polish and careful thought. Right now it looks good, but not
>>> professional.
>>>
>>> don't mean to sound negative, just being honest.
>>>
>>> On Tue, May 25, 2010 at 6:06 AM, Robin
>>> Komiwes<ro...@gmail.com> wrote:
>>>> I said some weeks ago that I will assist the documentation renew
>>>> effort by
>>>> proposing a redesign for Tapestry homepage.
>>>>
>>>> I'm quite satisfied with the first draft and I now need the community
>>>> feedback to know if I should stop or continue this way. Of course, if
>>>> someone wants to help on the content or the design, you are very
>>>> welcome.
>>>>
>>>> The URLs :
>>>> http://komiwes.fr/tapestry
>>>> http://komiwes.fr/tapestry/getting_started.htm
>>>> http://komiwes.fr/tapestry/community.htm
>>>>
>>>> Now, here are the key principles of this redesign. I've tried to follow
>>>> them, and some may need to be expressed more.
>>>>
>>>> - Everything is marketing
>>>> Others frameworks understand that well. They all have a shiny
>>>> homepage, with
>>>> key words, quotes from great people and baselines that you can't miss.
>>>>
>>>> The homepage should seduce and convince people. You've got to know
>>>> that the
>>>> framework you are using, or about to, is one of the best frameworks. In
>>>> fact, there are plenty of good frameworks, if you launch tomorrow
>>>> another
>>>> "good framework", you are already dead. You need to offer a rockstar
>>>> framework.
>>>>
>>>> On this redesign, a newcomer will be satisfied by how the
>>>> information is
>>>> clear and concise. He will know the concept of Tapestry (cf
>>>> baseline) and
>>>> will instantly have an idea of Tapestry strengths (cf Java power,
>>>> scripting
>>>> ease, highly productive).
>>>>
>>>> Finally he will be invited to give 20 minutes of its time to try the
>>>> framework and realize how true was what we announced before.
>>>>
>>>> - Community
>>>> Every framework should focus on its community. IMHO, that's another key
>>>> point: again, if you think that an open source framework will buzz just
>>>> because it is well made, you may have miss how the internet has evolved
>>>> since some years. Ruby on Rails and jQuery have integrated that
>>>> since the
>>>> beginning. Focusing on the community is mandatory. Why?
>>>>
>>>> First, because as a Web framework developer, you can't cover every
>>>> feature.
>>>> Web is just too big. Especially in the Java ecosystem. If someone
>>>> cover a
>>>> feature for you, thanks him and then do advertising for its
>>>> contribution as
>>>> it was one of the features of the framework. It should be presented
>>>> as a
>>>> part of the framework itself, not as "a nice side project that you
>>>> may look
>>>> to if you want to...".
>>>>
>>>> Secondly, because the web is social. If people feels that they are
>>>> part of
>>>> an active community, they will be proud of it and will wants to make
>>>> other
>>>> people joining it. They will blog for you, they will evangelize for
>>>> you. In
>>>> fact, they will to the marketing job for you.
>>>>
>>>> I think the effort on this point should be pushed a lot further. We
>>>> should
>>>> have some specs on how to write and provide components library, how to
>>>> provides plugins. We should have a place where to publish them.
>>>>
>>>> We should also have an open sourced keynote available to make
>>>> presentations
>>>> of Tapestry 5, like Howard's one :
>>>> http://www.slideshare.net/hlship/tapestry-5-java-power-scripting-ease
>>>> Everyone should be able to grab it and then do a presentation to its
>>>> local
>>>> JUG.
>>>>
>>>> - Fresh content
>>>> It's important to look like active. We all know here that Tapestry
>>>> is active
>>>> but if you look at the actual website, there is no clue about that.
>>>> Here, I think using a specific Twitter account (I've reserved
>>>> @tapestry_5)
>>>> for pushing news both on a social network and on the Tapestry
>>>> website would
>>>> be great. We would be able to easily push fresh, concise news from both
>>>> Tapestry 5 framework and any other related tweets.
>>>>
>>>> - Efficiency
>>>> One of the "cons" of maven sites is that they make you writing big
>>>> pages and
>>>> big menus. It is bad because it results in an insanely big amount of
>>>> data
>>>> that kills the data itself.
>>>> The homepage should be efficient and concise.
>>>>
>>>> - References
>>>> Real Tapestry applications showcase is a must have. We should be
>>>> able to say
>>>> "Hey, look! They've been using Tapestry in production and see how
>>>> nice it
>>>> works.". We already have some greats examples and we should show them.
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>
>>>
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [DISCUSS] Tapestry homepage redesign
Posted by Ulrich Stärk <ul...@spielviel.de>.
I'd configure confluence to auto-generate the contents with the new design included. Just a matter
of some tweaking once we've settled for a design.
Uli
On 25.05.2010 18:48, Howard Lewis Ship wrote:
> You are bringing tears to my eyes. This looks fantastic. I assume this
> is a replacement for http://tapestry.apache.org, right?
>
> Is this mock-up manually generated, or are you using some kind of
> script? Ideally this would be easy to regenerate and redeploy live,
> when changes occur. Also on the wish list, an RSS feed driven by a
> "News" tab. Perhaps we need some main tabs across the top (the
> current set) and some secondary tabs down the side (component
> reference, older releases, news, etc.).
>
> As a side note ... Widen (one of my clients) has donated some designer
> time to work on the Tapestry logo, which could urgently use some
> refreshing. We'll have a separate discussion to choose a new logo
> design (or stick with the current one, I suppose).
>
> On Tue, May 25, 2010 at 9:31 AM, Jesse Kuhnert<jk...@gmail.com> wrote:
>> Looks like a pretty good step in a new direction. Had a couple thoughts though:
>>
>> -) Something looks off on the tapestry word lettering of the banner
>> logo. I think it's the white edge on green background but don't know
>> what the graphic design fix should be.
>> -) The center aligned text in the boxes up top doesn't look quite
>> right either, should probably be left justified at least.
>> -) Don't like the font for some reason, even if it is what is already
>> used. How does helvetica look? =)
>> -) The text boxes or the headers above them just below the banner logo
>> should probably have links to something on the real site.
>>
>> Overall it does look like a great start though, just think it needs
>> more polish and careful thought. Right now it looks good, but not
>> professional.
>>
>> don't mean to sound negative, just being honest.
>>
>> On Tue, May 25, 2010 at 6:06 AM, Robin Komiwes<ro...@gmail.com> wrote:
>>> I said some weeks ago that I will assist the documentation renew effort by
>>> proposing a redesign for Tapestry homepage.
>>>
>>> I'm quite satisfied with the first draft and I now need the community
>>> feedback to know if I should stop or continue this way. Of course, if
>>> someone wants to help on the content or the design, you are very welcome.
>>>
>>> The URLs :
>>> http://komiwes.fr/tapestry
>>> http://komiwes.fr/tapestry/getting_started.htm
>>> http://komiwes.fr/tapestry/community.htm
>>>
>>> Now, here are the key principles of this redesign. I've tried to follow
>>> them, and some may need to be expressed more.
>>>
>>> - Everything is marketing
>>> Others frameworks understand that well. They all have a shiny homepage, with
>>> key words, quotes from great people and baselines that you can't miss.
>>>
>>> The homepage should seduce and convince people. You've got to know that the
>>> framework you are using, or about to, is one of the best frameworks. In
>>> fact, there are plenty of good frameworks, if you launch tomorrow another
>>> "good framework", you are already dead. You need to offer a rockstar
>>> framework.
>>>
>>> On this redesign, a newcomer will be satisfied by how the information is
>>> clear and concise. He will know the concept of Tapestry (cf baseline) and
>>> will instantly have an idea of Tapestry strengths (cf Java power, scripting
>>> ease, highly productive).
>>>
>>> Finally he will be invited to give 20 minutes of its time to try the
>>> framework and realize how true was what we announced before.
>>>
>>> - Community
>>> Every framework should focus on its community. IMHO, that's another key
>>> point: again, if you think that an open source framework will buzz just
>>> because it is well made, you may have miss how the internet has evolved
>>> since some years. Ruby on Rails and jQuery have integrated that since the
>>> beginning. Focusing on the community is mandatory. Why?
>>>
>>> First, because as a Web framework developer, you can't cover every feature.
>>> Web is just too big. Especially in the Java ecosystem. If someone cover a
>>> feature for you, thanks him and then do advertising for its contribution as
>>> it was one of the features of the framework. It should be presented as a
>>> part of the framework itself, not as "a nice side project that you may look
>>> to if you want to...".
>>>
>>> Secondly, because the web is social. If people feels that they are part of
>>> an active community, they will be proud of it and will wants to make other
>>> people joining it. They will blog for you, they will evangelize for you. In
>>> fact, they will to the marketing job for you.
>>>
>>> I think the effort on this point should be pushed a lot further. We should
>>> have some specs on how to write and provide components library, how to
>>> provides plugins. We should have a place where to publish them.
>>>
>>> We should also have an open sourced keynote available to make presentations
>>> of Tapestry 5, like Howard's one :
>>> http://www.slideshare.net/hlship/tapestry-5-java-power-scripting-ease
>>> Everyone should be able to grab it and then do a presentation to its local
>>> JUG.
>>>
>>> - Fresh content
>>> It's important to look like active. We all know here that Tapestry is active
>>> but if you look at the actual website, there is no clue about that.
>>> Here, I think using a specific Twitter account (I've reserved @tapestry_5)
>>> for pushing news both on a social network and on the Tapestry website would
>>> be great. We would be able to easily push fresh, concise news from both
>>> Tapestry 5 framework and any other related tweets.
>>>
>>> - Efficiency
>>> One of the "cons" of maven sites is that they make you writing big pages and
>>> big menus. It is bad because it results in an insanely big amount of data
>>> that kills the data itself.
>>> The homepage should be efficient and concise.
>>>
>>> - References
>>> Real Tapestry applications showcase is a must have. We should be able to say
>>> "Hey, look! They've been using Tapestry in production and see how nice it
>>> works.". We already have some greats examples and we should show them.
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>
>>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [DISCUSS] Tapestry homepage redesign
Posted by "Thiago H. de Paula Figueiredo" <th...@gmail.com>.
On Wed, 26 May 2010 06:52:24 -0300, Andreas Andreou <an...@di.uoa.gr>
wrote:
> wrt logo, i only just came accross
> http://blog.tapestry5.de/index.php/2010/05/17/new-tapestry-logo/
> from Igor's blog. According to him it's just a joke, but a cool one in
> my eyes
It's cool, but Ferrari must have a lot of lawyers . . .
--
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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [DISCUSS] Tapestry homepage redesign
Posted by Massimo Lusetti <ml...@gmail.com>.
On Wed, May 26, 2010 at 11:52 AM, Andreas Andreou <an...@di.uoa.gr> wrote:
> wrt logo, i only just came accross
> http://blog.tapestry5.de/index.php/2010/05/17/new-tapestry-logo/
> from Igor's blog. According to him it's just a joke, but a cool one in my eyes
I don't think it will be usable ;)
--
Massimo
http://meridio.blogspot.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [DISCUSS] Tapestry homepage redesign
Posted by Andreas Andreou <an...@di.uoa.gr>.
wrt logo, i only just came accross
http://blog.tapestry5.de/index.php/2010/05/17/new-tapestry-logo/
from Igor's blog. According to him it's just a joke, but a cool one in my eyes
On Tue, May 25, 2010 at 19:48, Howard Lewis Ship <hl...@gmail.com> wrote:
> You are bringing tears to my eyes. This looks fantastic. I assume this
> is a replacement for http://tapestry.apache.org, right?
>
> Is this mock-up manually generated, or are you using some kind of
> script? Ideally this would be easy to regenerate and redeploy live,
> when changes occur. Also on the wish list, an RSS feed driven by a
> "News" tab. Perhaps we need some main tabs across the top (the
> current set) and some secondary tabs down the side (component
> reference, older releases, news, etc.).
>
> As a side note ... Widen (one of my clients) has donated some designer
> time to work on the Tapestry logo, which could urgently use some
> refreshing. We'll have a separate discussion to choose a new logo
> design (or stick with the current one, I suppose).
>
> On Tue, May 25, 2010 at 9:31 AM, Jesse Kuhnert <jk...@gmail.com> wrote:
>> Looks like a pretty good step in a new direction. Had a couple thoughts though:
>>
>> -) Something looks off on the tapestry word lettering of the banner
>> logo. I think it's the white edge on green background but don't know
>> what the graphic design fix should be.
>> -) The center aligned text in the boxes up top doesn't look quite
>> right either, should probably be left justified at least.
>> -) Don't like the font for some reason, even if it is what is already
>> used. How does helvetica look? =)
>> -) The text boxes or the headers above them just below the banner logo
>> should probably have links to something on the real site.
>>
>> Overall it does look like a great start though, just think it needs
>> more polish and careful thought. Right now it looks good, but not
>> professional.
>>
>> don't mean to sound negative, just being honest.
>>
>> On Tue, May 25, 2010 at 6:06 AM, Robin Komiwes <ro...@gmail.com> wrote:
>>> I said some weeks ago that I will assist the documentation renew effort by
>>> proposing a redesign for Tapestry homepage.
>>>
>>> I'm quite satisfied with the first draft and I now need the community
>>> feedback to know if I should stop or continue this way. Of course, if
>>> someone wants to help on the content or the design, you are very welcome.
>>>
>>> The URLs :
>>> http://komiwes.fr/tapestry
>>> http://komiwes.fr/tapestry/getting_started.htm
>>> http://komiwes.fr/tapestry/community.htm
>>>
>>> Now, here are the key principles of this redesign. I've tried to follow
>>> them, and some may need to be expressed more.
>>>
>>> - Everything is marketing
>>> Others frameworks understand that well. They all have a shiny homepage, with
>>> key words, quotes from great people and baselines that you can't miss.
>>>
>>> The homepage should seduce and convince people. You've got to know that the
>>> framework you are using, or about to, is one of the best frameworks. In
>>> fact, there are plenty of good frameworks, if you launch tomorrow another
>>> "good framework", you are already dead. You need to offer a rockstar
>>> framework.
>>>
>>> On this redesign, a newcomer will be satisfied by how the information is
>>> clear and concise. He will know the concept of Tapestry (cf baseline) and
>>> will instantly have an idea of Tapestry strengths (cf Java power, scripting
>>> ease, highly productive).
>>>
>>> Finally he will be invited to give 20 minutes of its time to try the
>>> framework and realize how true was what we announced before.
>>>
>>> - Community
>>> Every framework should focus on its community. IMHO, that's another key
>>> point: again, if you think that an open source framework will buzz just
>>> because it is well made, you may have miss how the internet has evolved
>>> since some years. Ruby on Rails and jQuery have integrated that since the
>>> beginning. Focusing on the community is mandatory. Why?
>>>
>>> First, because as a Web framework developer, you can't cover every feature.
>>> Web is just too big. Especially in the Java ecosystem. If someone cover a
>>> feature for you, thanks him and then do advertising for its contribution as
>>> it was one of the features of the framework. It should be presented as a
>>> part of the framework itself, not as "a nice side project that you may look
>>> to if you want to...".
>>>
>>> Secondly, because the web is social. If people feels that they are part of
>>> an active community, they will be proud of it and will wants to make other
>>> people joining it. They will blog for you, they will evangelize for you. In
>>> fact, they will to the marketing job for you.
>>>
>>> I think the effort on this point should be pushed a lot further. We should
>>> have some specs on how to write and provide components library, how to
>>> provides plugins. We should have a place where to publish them.
>>>
>>> We should also have an open sourced keynote available to make presentations
>>> of Tapestry 5, like Howard's one :
>>> http://www.slideshare.net/hlship/tapestry-5-java-power-scripting-ease
>>> Everyone should be able to grab it and then do a presentation to its local
>>> JUG.
>>>
>>> - Fresh content
>>> It's important to look like active. We all know here that Tapestry is active
>>> but if you look at the actual website, there is no clue about that.
>>> Here, I think using a specific Twitter account (I've reserved @tapestry_5)
>>> for pushing news both on a social network and on the Tapestry website would
>>> be great. We would be able to easily push fresh, concise news from both
>>> Tapestry 5 framework and any other related tweets.
>>>
>>> - Efficiency
>>> One of the "cons" of maven sites is that they make you writing big pages and
>>> big menus. It is bad because it results in an insanely big amount of data
>>> that kills the data itself.
>>> The homepage should be efficient and concise.
>>>
>>> - References
>>> Real Tapestry applications showcase is a must have. We should be able to say
>>> "Hey, look! They've been using Tapestry in production and see how nice it
>>> works.". We already have some greats examples and we should show them.
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>
>>
>
>
>
> --
> Howard M. Lewis Ship
>
> Creator of Apache Tapestry
>
> The source for Tapestry training, mentoring and support. Contact me to
> learn how I can get you up and productive in Tapestry fast!
>
> (971) 678-5210
> http://howardlewisship.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
--
Andreas Andreou - andyhot@apache.org - http://blog.andyhot.gr
Tapestry / Tacos developer
Open Source / JEE Consulting
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [DISCUSS] Tapestry homepage redesign
Posted by Howard Lewis Ship <hl...@gmail.com>.
You are bringing tears to my eyes. This looks fantastic. I assume this
is a replacement for http://tapestry.apache.org, right?
Is this mock-up manually generated, or are you using some kind of
script? Ideally this would be easy to regenerate and redeploy live,
when changes occur. Also on the wish list, an RSS feed driven by a
"News" tab. Perhaps we need some main tabs across the top (the
current set) and some secondary tabs down the side (component
reference, older releases, news, etc.).
As a side note ... Widen (one of my clients) has donated some designer
time to work on the Tapestry logo, which could urgently use some
refreshing. We'll have a separate discussion to choose a new logo
design (or stick with the current one, I suppose).
On Tue, May 25, 2010 at 9:31 AM, Jesse Kuhnert <jk...@gmail.com> wrote:
> Looks like a pretty good step in a new direction. Had a couple thoughts though:
>
> -) Something looks off on the tapestry word lettering of the banner
> logo. I think it's the white edge on green background but don't know
> what the graphic design fix should be.
> -) The center aligned text in the boxes up top doesn't look quite
> right either, should probably be left justified at least.
> -) Don't like the font for some reason, even if it is what is already
> used. How does helvetica look? =)
> -) The text boxes or the headers above them just below the banner logo
> should probably have links to something on the real site.
>
> Overall it does look like a great start though, just think it needs
> more polish and careful thought. Right now it looks good, but not
> professional.
>
> don't mean to sound negative, just being honest.
>
> On Tue, May 25, 2010 at 6:06 AM, Robin Komiwes <ro...@gmail.com> wrote:
>> I said some weeks ago that I will assist the documentation renew effort by
>> proposing a redesign for Tapestry homepage.
>>
>> I'm quite satisfied with the first draft and I now need the community
>> feedback to know if I should stop or continue this way. Of course, if
>> someone wants to help on the content or the design, you are very welcome.
>>
>> The URLs :
>> http://komiwes.fr/tapestry
>> http://komiwes.fr/tapestry/getting_started.htm
>> http://komiwes.fr/tapestry/community.htm
>>
>> Now, here are the key principles of this redesign. I've tried to follow
>> them, and some may need to be expressed more.
>>
>> - Everything is marketing
>> Others frameworks understand that well. They all have a shiny homepage, with
>> key words, quotes from great people and baselines that you can't miss.
>>
>> The homepage should seduce and convince people. You've got to know that the
>> framework you are using, or about to, is one of the best frameworks. In
>> fact, there are plenty of good frameworks, if you launch tomorrow another
>> "good framework", you are already dead. You need to offer a rockstar
>> framework.
>>
>> On this redesign, a newcomer will be satisfied by how the information is
>> clear and concise. He will know the concept of Tapestry (cf baseline) and
>> will instantly have an idea of Tapestry strengths (cf Java power, scripting
>> ease, highly productive).
>>
>> Finally he will be invited to give 20 minutes of its time to try the
>> framework and realize how true was what we announced before.
>>
>> - Community
>> Every framework should focus on its community. IMHO, that's another key
>> point: again, if you think that an open source framework will buzz just
>> because it is well made, you may have miss how the internet has evolved
>> since some years. Ruby on Rails and jQuery have integrated that since the
>> beginning. Focusing on the community is mandatory. Why?
>>
>> First, because as a Web framework developer, you can't cover every feature.
>> Web is just too big. Especially in the Java ecosystem. If someone cover a
>> feature for you, thanks him and then do advertising for its contribution as
>> it was one of the features of the framework. It should be presented as a
>> part of the framework itself, not as "a nice side project that you may look
>> to if you want to...".
>>
>> Secondly, because the web is social. If people feels that they are part of
>> an active community, they will be proud of it and will wants to make other
>> people joining it. They will blog for you, they will evangelize for you. In
>> fact, they will to the marketing job for you.
>>
>> I think the effort on this point should be pushed a lot further. We should
>> have some specs on how to write and provide components library, how to
>> provides plugins. We should have a place where to publish them.
>>
>> We should also have an open sourced keynote available to make presentations
>> of Tapestry 5, like Howard's one :
>> http://www.slideshare.net/hlship/tapestry-5-java-power-scripting-ease
>> Everyone should be able to grab it and then do a presentation to its local
>> JUG.
>>
>> - Fresh content
>> It's important to look like active. We all know here that Tapestry is active
>> but if you look at the actual website, there is no clue about that.
>> Here, I think using a specific Twitter account (I've reserved @tapestry_5)
>> for pushing news both on a social network and on the Tapestry website would
>> be great. We would be able to easily push fresh, concise news from both
>> Tapestry 5 framework and any other related tweets.
>>
>> - Efficiency
>> One of the "cons" of maven sites is that they make you writing big pages and
>> big menus. It is bad because it results in an insanely big amount of data
>> that kills the data itself.
>> The homepage should be efficient and concise.
>>
>> - References
>> Real Tapestry applications showcase is a must have. We should be able to say
>> "Hey, look! They've been using Tapestry in production and see how nice it
>> works.". We already have some greats examples and we should show them.
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!
(971) 678-5210
http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [DISCUSS] Tapestry homepage redesign
Posted by Ulrich Stärk <ul...@spielviel.de>.
On 25.05.2010 18:31, Jesse Kuhnert wrote:
> Looks like a pretty good step in a new direction. Had a couple thoughts though:
>
> -) Something looks off on the tapestry word lettering of the banner
> logo. I think it's the white edge on green background but don't know
> what the graphic design fix should be.
That's probably because the text was extracted from the logo image. The font is called Din17 which
isn't freely available so all Robin could do was extract the existing text.
Uli
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [DISCUSS] Tapestry homepage redesign
Posted by Jesse Kuhnert <jk...@gmail.com>.
Looks like a pretty good step in a new direction. Had a couple thoughts though:
-) Something looks off on the tapestry word lettering of the banner
logo. I think it's the white edge on green background but don't know
what the graphic design fix should be.
-) The center aligned text in the boxes up top doesn't look quite
right either, should probably be left justified at least.
-) Don't like the font for some reason, even if it is what is already
used. How does helvetica look? =)
-) The text boxes or the headers above them just below the banner logo
should probably have links to something on the real site.
Overall it does look like a great start though, just think it needs
more polish and careful thought. Right now it looks good, but not
professional.
don't mean to sound negative, just being honest.
On Tue, May 25, 2010 at 6:06 AM, Robin Komiwes <ro...@gmail.com> wrote:
> I said some weeks ago that I will assist the documentation renew effort by
> proposing a redesign for Tapestry homepage.
>
> I'm quite satisfied with the first draft and I now need the community
> feedback to know if I should stop or continue this way. Of course, if
> someone wants to help on the content or the design, you are very welcome.
>
> The URLs :
> http://komiwes.fr/tapestry
> http://komiwes.fr/tapestry/getting_started.htm
> http://komiwes.fr/tapestry/community.htm
>
> Now, here are the key principles of this redesign. I've tried to follow
> them, and some may need to be expressed more.
>
> - Everything is marketing
> Others frameworks understand that well. They all have a shiny homepage, with
> key words, quotes from great people and baselines that you can't miss.
>
> The homepage should seduce and convince people. You've got to know that the
> framework you are using, or about to, is one of the best frameworks. In
> fact, there are plenty of good frameworks, if you launch tomorrow another
> "good framework", you are already dead. You need to offer a rockstar
> framework.
>
> On this redesign, a newcomer will be satisfied by how the information is
> clear and concise. He will know the concept of Tapestry (cf baseline) and
> will instantly have an idea of Tapestry strengths (cf Java power, scripting
> ease, highly productive).
>
> Finally he will be invited to give 20 minutes of its time to try the
> framework and realize how true was what we announced before.
>
> - Community
> Every framework should focus on its community. IMHO, that's another key
> point: again, if you think that an open source framework will buzz just
> because it is well made, you may have miss how the internet has evolved
> since some years. Ruby on Rails and jQuery have integrated that since the
> beginning. Focusing on the community is mandatory. Why?
>
> First, because as a Web framework developer, you can't cover every feature.
> Web is just too big. Especially in the Java ecosystem. If someone cover a
> feature for you, thanks him and then do advertising for its contribution as
> it was one of the features of the framework. It should be presented as a
> part of the framework itself, not as "a nice side project that you may look
> to if you want to...".
>
> Secondly, because the web is social. If people feels that they are part of
> an active community, they will be proud of it and will wants to make other
> people joining it. They will blog for you, they will evangelize for you. In
> fact, they will to the marketing job for you.
>
> I think the effort on this point should be pushed a lot further. We should
> have some specs on how to write and provide components library, how to
> provides plugins. We should have a place where to publish them.
>
> We should also have an open sourced keynote available to make presentations
> of Tapestry 5, like Howard's one :
> http://www.slideshare.net/hlship/tapestry-5-java-power-scripting-ease
> Everyone should be able to grab it and then do a presentation to its local
> JUG.
>
> - Fresh content
> It's important to look like active. We all know here that Tapestry is active
> but if you look at the actual website, there is no clue about that.
> Here, I think using a specific Twitter account (I've reserved @tapestry_5)
> for pushing news both on a social network and on the Tapestry website would
> be great. We would be able to easily push fresh, concise news from both
> Tapestry 5 framework and any other related tweets.
>
> - Efficiency
> One of the "cons" of maven sites is that they make you writing big pages and
> big menus. It is bad because it results in an insanely big amount of data
> that kills the data itself.
> The homepage should be efficient and concise.
>
> - References
> Real Tapestry applications showcase is a must have. We should be able to say
> "Hey, look! They've been using Tapestry in production and see how nice it
> works.". We already have some greats examples and we should show them.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [DISCUSS] Tapestry homepage redesign
Posted by Igor Drobiazko <ig...@gmail.com>.
Good job. Looks great. I agree with all the principles and love the design.
On Tue, May 25, 2010 at 12:06 PM, Robin Komiwes <ro...@gmail.com>wrote:
> I said some weeks ago that I will assist the documentation renew effort by
> proposing a redesign for Tapestry homepage.
>
> I'm quite satisfied with the first draft and I now need the community
> feedback to know if I should stop or continue this way. Of course, if
> someone wants to help on the content or the design, you are very welcome.
>
> The URLs :
> http://komiwes.fr/tapestry
> http://komiwes.fr/tapestry/getting_started.htm
> http://komiwes.fr/tapestry/community.htm
>
> Now, here are the key principles of this redesign. I've tried to follow
> them, and some may need to be expressed more.
>
> - Everything is marketing
> Others frameworks understand that well. They all have a shiny homepage,
> with
> key words, quotes from great people and baselines that you can't miss.
>
> The homepage should seduce and convince people. You've got to know that the
> framework you are using, or about to, is one of the best frameworks. In
> fact, there are plenty of good frameworks, if you launch tomorrow another
> "good framework", you are already dead. You need to offer a rockstar
> framework.
>
> On this redesign, a newcomer will be satisfied by how the information is
> clear and concise. He will know the concept of Tapestry (cf baseline) and
> will instantly have an idea of Tapestry strengths (cf Java power,
> scripting
> ease, highly productive).
>
> Finally he will be invited to give 20 minutes of its time to try the
> framework and realize how true was what we announced before.
>
> - Community
> Every framework should focus on its community. IMHO, that's another key
> point: again, if you think that an open source framework will buzz just
> because it is well made, you may have miss how the internet has evolved
> since some years. Ruby on Rails and jQuery have integrated that since the
> beginning. Focusing on the community is mandatory. Why?
>
> First, because as a Web framework developer, you can't cover every feature.
> Web is just too big. Especially in the Java ecosystem. If someone cover a
> feature for you, thanks him and then do advertising for its contribution as
> it was one of the features of the framework. It should be presented as a
> part of the framework itself, not as "a nice side project that you may look
> to if you want to...".
>
> Secondly, because the web is social. If people feels that they are part of
> an active community, they will be proud of it and will wants to make other
> people joining it. They will blog for you, they will evangelize for you. In
> fact, they will to the marketing job for you.
>
> I think the effort on this point should be pushed a lot further. We should
> have some specs on how to write and provide components library, how to
> provides plugins. We should have a place where to publish them.
>
> We should also have an open sourced keynote available to make presentations
> of Tapestry 5, like Howard's one :
> http://www.slideshare.net/hlship/tapestry-5-java-power-scripting-ease
> Everyone should be able to grab it and then do a presentation to its local
> JUG.
>
> - Fresh content
> It's important to look like active. We all know here that Tapestry is
> active
> but if you look at the actual website, there is no clue about that.
> Here, I think using a specific Twitter account (I've reserved @tapestry_5)
> for pushing news both on a social network and on the Tapestry website would
> be great. We would be able to easily push fresh, concise news from both
> Tapestry 5 framework and any other related tweets.
>
> - Efficiency
> One of the "cons" of maven sites is that they make you writing big pages
> and
> big menus. It is bad because it results in an insanely big amount of data
> that kills the data itself.
> The homepage should be efficient and concise.
>
> - References
> Real Tapestry applications showcase is a must have. We should be able to
> say
> "Hey, look! They've been using Tapestry in production and see how nice it
> works.". We already have some greats examples and we should show them.
>
--
Best regards,
Igor Drobiazko
http://tapestry5.de/blog
Re: [DISCUSS] Tapestry homepage redesign
Posted by Lubor Gajda <lu...@gmail.com>.
I would simplify it even more and use cleaner marketing points (Why
Tapestry?/Download/Learn/Get Involved). Check this site http://jruby.org,
it's very good example how the Tapestry homepage could look like.
Returning users could go directly to documentation related page and don't
bother with the homepage.
On Tue, May 25, 2010 at 11:06 AM, Robin Komiwes <ro...@gmail.com>wrote:
> I said some weeks ago that I will assist the documentation renew effort by
> proposing a redesign for Tapestry homepage.
>
> I'm quite satisfied with the first draft and I now need the community
> feedback to know if I should stop or continue this way. Of course, if
> someone wants to help on the content or the design, you are very welcome.
>
> The URLs :
> http://komiwes.fr/tapestry
> http://komiwes.fr/tapestry/getting_started.htm
> http://komiwes.fr/tapestry/community.htm
>
> Now, here are the key principles of this redesign. I've tried to follow
> them, and some may need to be expressed more.
>
> - Everything is marketing
> Others frameworks understand that well. They all have a shiny homepage,
> with
> key words, quotes from great people and baselines that you can't miss.
>
> The homepage should seduce and convince people. You've got to know that the
> framework you are using, or about to, is one of the best frameworks. In
> fact, there are plenty of good frameworks, if you launch tomorrow another
> "good framework", you are already dead. You need to offer a rockstar
> framework.
>
> On this redesign, a newcomer will be satisfied by how the information is
> clear and concise. He will know the concept of Tapestry (cf baseline) and
> will instantly have an idea of Tapestry strengths (cf Java power,
> scripting
> ease, highly productive).
>
> Finally he will be invited to give 20 minutes of its time to try the
> framework and realize how true was what we announced before.
>
> - Community
> Every framework should focus on its community. IMHO, that's another key
> point: again, if you think that an open source framework will buzz just
> because it is well made, you may have miss how the internet has evolved
> since some years. Ruby on Rails and jQuery have integrated that since the
> beginning. Focusing on the community is mandatory. Why?
>
> First, because as a Web framework developer, you can't cover every feature.
> Web is just too big. Especially in the Java ecosystem. If someone cover a
> feature for you, thanks him and then do advertising for its contribution as
> it was one of the features of the framework. It should be presented as a
> part of the framework itself, not as "a nice side project that you may look
> to if you want to...".
>
> Secondly, because the web is social. If people feels that they are part of
> an active community, they will be proud of it and will wants to make other
> people joining it. They will blog for you, they will evangelize for you. In
> fact, they will to the marketing job for you.
>
> I think the effort on this point should be pushed a lot further. We should
> have some specs on how to write and provide components library, how to
> provides plugins. We should have a place where to publish them.
>
> We should also have an open sourced keynote available to make presentations
> of Tapestry 5, like Howard's one :
> http://www.slideshare.net/hlship/tapestry-5-java-power-scripting-ease
> Everyone should be able to grab it and then do a presentation to its local
> JUG.
>
> - Fresh content
> It's important to look like active. We all know here that Tapestry is
> active
> but if you look at the actual website, there is no clue about that.
> Here, I think using a specific Twitter account (I've reserved @tapestry_5)
> for pushing news both on a social network and on the Tapestry website would
> be great. We would be able to easily push fresh, concise news from both
> Tapestry 5 framework and any other related tweets.
>
> - Efficiency
> One of the "cons" of maven sites is that they make you writing big pages
> and
> big menus. It is bad because it results in an insanely big amount of data
> that kills the data itself.
> The homepage should be efficient and concise.
>
> - References
> Real Tapestry applications showcase is a must have. We should be able to
> say
> "Hey, look! They've been using Tapestry in production and see how nice it
> works.". We already have some greats examples and we should show them.
>
Re: [DISCUSS] Tapestry homepage redesign
Posted by Kristian Marinkovic <kr...@porsche.co.at>.
hi robin,
i love the new design!
in response to ulrichs suggestion, we could make
the first row of links look like tabs... as seen on
www.hibernate.org. it might be more visible then.
g,
kris
Von: Robin Komiwes <ro...@gmail.com>
An: Tapestry development <de...@tapestry.apache.org>
Datum: 25.05.2010 12:06
Betreff: [DISCUSS] Tapestry homepage redesign
Gesendet von: odisseus@gmail.com
I said some weeks ago that I will assist the documentation renew effort by
proposing a redesign for Tapestry homepage.
I'm quite satisfied with the first draft and I now need the community
feedback to know if I should stop or continue this way. Of course, if
someone wants to help on the content or the design, you are very welcome.
The URLs :
http://komiwes.fr/tapestry
http://komiwes.fr/tapestry/getting_started.htm
http://komiwes.fr/tapestry/community.htm
Now, here are the key principles of this redesign. I've tried to follow
them, and some may need to be expressed more.
- Everything is marketing
Others frameworks understand that well. They all have a shiny homepage,
with
key words, quotes from great people and baselines that you can't miss.
The homepage should seduce and convince people. You've got to know that
the
framework you are using, or about to, is one of the best frameworks. In
fact, there are plenty of good frameworks, if you launch tomorrow another
"good framework", you are already dead. You need to offer a rockstar
framework.
On this redesign, a newcomer will be satisfied by how the information is
clear and concise. He will know the concept of Tapestry (cf baseline) and
will instantly have an idea of Tapestry strengths (cf Java power,
scripting
ease, highly productive).
Finally he will be invited to give 20 minutes of its time to try the
framework and realize how true was what we announced before.
- Community
Every framework should focus on its community. IMHO, that's another key
point: again, if you think that an open source framework will buzz just
because it is well made, you may have miss how the internet has evolved
since some years. Ruby on Rails and jQuery have integrated that since the
beginning. Focusing on the community is mandatory. Why?
First, because as a Web framework developer, you can't cover every
feature.
Web is just too big. Especially in the Java ecosystem. If someone cover a
feature for you, thanks him and then do advertising for its contribution
as
it was one of the features of the framework. It should be presented as a
part of the framework itself, not as "a nice side project that you may
look
to if you want to...".
Secondly, because the web is social. If people feels that they are part of
an active community, they will be proud of it and will wants to make other
people joining it. They will blog for you, they will evangelize for you.
In
fact, they will to the marketing job for you.
I think the effort on this point should be pushed a lot further. We should
have some specs on how to write and provide components library, how to
provides plugins. We should have a place where to publish them.
We should also have an open sourced keynote available to make
presentations
of Tapestry 5, like Howard's one :
http://www.slideshare.net/hlship/tapestry-5-java-power-scripting-ease
Everyone should be able to grab it and then do a presentation to its local
JUG.
- Fresh content
It's important to look like active. We all know here that Tapestry is
active
but if you look at the actual website, there is no clue about that.
Here, I think using a specific Twitter account (I've reserved @tapestry_5)
for pushing news both on a social network and on the Tapestry website
would
be great. We would be able to easily push fresh, concise news from both
Tapestry 5 framework and any other related tweets.
- Efficiency
One of the "cons" of maven sites is that they make you writing big pages
and
big menus. It is bad because it results in an insanely big amount of data
that kills the data itself.
The homepage should be efficient and concise.
- References
Real Tapestry applications showcase is a must have. We should be able to
say
"Hey, look! They've been using Tapestry in production and see how nice it
works.". We already have some greats examples and we should show them.
Re: [DISCUSS] Tapestry homepage redesign
Posted by "Thiago H. de Paula Figueiredo" <th...@gmail.com>.
On Tue, 25 May 2010 07:06:03 -0300, Robin Komiwes
<ro...@gmail.com> wrote:
> I said some weeks ago that I will assist the documentation renew effort
> by proposing a redesign for Tapestry homepage.
>
> I'm quite satisfied with the first draft and I now need the community
> feedback to know if I should stop or continue this way. Of course, if
> someone wants to help on the content or the design, you are very welcome.
>
> The URLs :
> http://komiwes.fr/tapestry
> http://komiwes.fr/tapestry/getting_started.htm
> http://komiwes.fr/tapestry/community.htm
I love it! :) Congratulations, Robin!
--
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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [DISCUSS] Tapestry homepage redesign
Posted by Andreas Andreou <an...@di.uoa.gr>.
I like it a lot too - the first few pages should be exactly like that
(just marketing).
Top links look fine to me (though still arguing with myself if it should read
"Download Latest Version" vs. "Download Tapestry 5.2.0"
I'm also clearly in favor of some social or buzz features in the front page -
twitter is fine, i was also considering having the titles of the last few mails
from this list.
Though it's still an open question how this will work at the apache
servers (i.e.
in static pages)... will it be js widgets ?
Nice work & initiative
On Tue, May 25, 2010 at 14:34, Piero Sartini <li...@pierosartini.de> wrote:
> Great work! I like this design very much.
>
> I am with Ulrich that the menu could be more visible. What is not
> neccessary in my oppinion is to have the JavaDocs and other stuff
> visible in the main menu - its enough to have them somewhere under
> "Documentation". Speaking about such "content pages", I see the need
> of a sub navigation.
>
> Speaking about the key features on the starting page - what do you
> think about some possibility like "see all features". This would lead
> to a dedicated page explaining more of tapestry's features. On most
> new frameworks thats the first page I am searching for to get a more
> complete overview.
>
> About the twitter stuff:
> Wouldn't it be better to include all tweets tagged with, say,
> #tapestry5 or #tap5? This way the tapestry site would present all
> people twittering about tapestry - not just one official account.
>
> If your twitter box is just intended to present news, I would rather
> maintain them through confluence - twitter would be just another
> tool/account to take care of.
>
> Piero
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
--
Andreas Andreou - andyhot@apache.org - http://blog.andyhot.gr
Tapestry / Tacos developer
Open Source / JEE Consulting
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [DISCUSS] Tapestry homepage redesign
Posted by Piero Sartini <li...@pierosartini.de>.
Great work! I like this design very much.
I am with Ulrich that the menu could be more visible. What is not
neccessary in my oppinion is to have the JavaDocs and other stuff
visible in the main menu - its enough to have them somewhere under
"Documentation". Speaking about such "content pages", I see the need
of a sub navigation.
Speaking about the key features on the starting page - what do you
think about some possibility like "see all features". This would lead
to a dedicated page explaining more of tapestry's features. On most
new frameworks thats the first page I am searching for to get a more
complete overview.
About the twitter stuff:
Wouldn't it be better to include all tweets tagged with, say,
#tapestry5 or #tap5? This way the tapestry site would present all
people twittering about tapestry - not just one official account.
If your twitter box is just intended to present news, I would rather
maintain them through confluence - twitter would be just another
tool/account to take care of.
Piero
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org