[Epo-marketing] Page CTAs

[Christopher Nehren]

On Wed, Jan 21, 2009 at 21:24:41 -0600 , Cory G Watson wrote:
> So the current idea is to have a series of simple Calls To Action  
> (henceforth, CTAs) on the front page.  Here's a simple mockup:
>
> http://img.skitch.com/20090122-tjsmc7nssu7r4s4cx6dm5g5hef.png
>
> I like 3, as it's got a nice symmetry.
>
> So the question is, what should these 3 things be?
>
> In mockups I've been using: Learn, Download and Contribute
>
> Learn: Here's where we put a 10,000ft FAQ with maybe a section for each 
> target audience.  Maybe at the top a set of boxes, one for each type... 
> Developer, Manager, CEO.  Then we put a blurb (#developer, etc) that 
> explains what the EPO can do for that segment.
>
> Download: Instructions and info for "getting" EPO.  We could break this up 
> (again) into sections: EC, Dist, etc.  I know we don't have this, but we 
> can put our plans on here for when it IS available.
>
> Contribute: Again with the segments.  Developer, Manager, CEO.  We write a 
> special blurb for each.
>
> Comments?  I think I can knock all this out on Friday->Sunday.  I'd like 
> some discussion to happen now so that there's less bikeshedding  
> afterward.

I like it. It's to the point, and more importantly, *simple*. Everything
one would want to do is encompassed in one of those three categories.
That way the user can select what they want to do and drill-down deeper
into that particular section. While I malign the aesthetics of sites
like twitter, I will laude them on their adherence to the difficult task
of simplicity in design. And so on about how simplicity is inviting,
etc. :)

What about contact info? Where would this fit? I can see it fitting
under learning ("I have a question...") but also contributing ("I want
to donate big money, whom do I talk to?"). The CTAs are great, but in
the event that they don't answer everyone's questions, I think it's
imperative that we make contact info very visible. Contact info
visibility seems to be of high importance for EPO considering part of
our goal (as I see them) is to listen to people's thoughts about why
Perl sucks and then respond.

-- 
Thanks and best regards,
Christopher Nehren