[zamalek]

> The ones that seek to know more are the ones they want to engage.

GWT is a solution, not a community. It might have a community behind it, but some poor soul might land up on that page with the only intent of getting shit done within the scope of their own job.

The ultimate core goal of GWT is to save people time: that is why developers write frameworks. Why should someone have to waste time [struggle to learn the purpose of 'framework X'] in order to save time [use 'framework X'].

Saving people time starts on your landing page. They need to be able to accept or reject your framework with as little further research as possible. "This is what our product does, here are some people who use it, this is what people say." Once people know that you can carry on with the more floral explanations.

[yitchelle]

Thanks for the explanation. The collective wisdom of HN is right on having a landing page with a couple of short sentences on what GWT is all about.