I rather like the 'For the impatient' part on the Enyo 
website: http://enyojs.com/about/

A quick and simple example is usually the best way to communicate the value 
proposition of a framework. By contrast, the landing page is rather generic 
and inexpressive. I say put a quick example right on the landing page. That 
way you probably have the biggest change of catching a developers 
attention, especially if the framework is as unique as Polymer.

Oh, and please don't use a carousel! http://shouldiuseacarousel.com/

On Monday, March 24, 2014 9:59:28 PM UTC+1, Eric Bidelman wrote:
>
> Joachim, I couldn't agree more. The homepage needs a value proposition. 
> It's currently buried a bit in subpages. Also, not many people understand 
> (yet) the value and features that web components unlocks. 
>
> Addy mentioned, we're hoping to get up some code up on the homepage to 
> help tell that story. Stay tuned!
>
>
> On Thu, Mar 20, 2014 at 7:30 AM, Addy Osmani <[email protected]<javascript:>
> > wrote:
>
>> Thanks for the detailed feedback. 
>>
>> We're looking at how we can better improve the messaging on the site and 
>> Eric has definitely been heavily involved in helping us craft what we have 
>> so far. Something the homepage currently lacks is a set of examples that 
>> really bring home the set of features that get developers excited about 
>> Polymer. We're working on a code concepts carousel / area that can 
>> highlight this so it's visible before you dive into the rest of the site.
>>
>> This would (I believe) also solve the lack of coverage of features like 
>> data binding earlier on in the experience.
>>
>>
>> On Thursday, 20 March 2014 07:56:05 UTC, Joachim Wester wrote:
>>>
>>> The 2011 presentation of MDV by Rafael Weinstein was also to the point. 
>>> Now, the {{binding}} stuff is well hidden if you're not looking for it.
>>>
>>  Follow Polymer on Google+: plus.google.com/107187849809354688692
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "Polymer" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected] <javascript:>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/polymer-dev/61ab09e5-d67f-4ac4-a2e8-893b5a13018d%40googlegroups.com<https://groups.google.com/d/msgid/polymer-dev/61ab09e5-d67f-4ac4-a2e8-893b5a13018d%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

Follow Polymer on Google+: plus.google.com/107187849809354688692
--- 
You received this message because you are subscribed to the Google Groups 
"Polymer" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/polymer-dev/59310457-bfdb-4038-84c0-0aeb570279ef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to