[aerogear-dev] Home page content rework

[Hylke Bons]

Hey Kris,

On 24/05/2013 18:40, Kris Borchers wrote:
> We are not specific to any back end so we won't mention JBoss here.
>> Get started with a library for your platform…
> Is that line really necessary?

Right now, it's not very clear where these buttons will take you. 
Visitors can find out, but it's friendlier to point out where you're 
going to be taken in advance. "'Javascript', 'Android' what?".

>> [[---platform buttons here---]]
>>
>> == Why? ==
> Again, is this necessary? What does it add? Both of those lines add more vertical scroll on mobile devices so I don't see the benefit, if any, outweighing that.

To transition from the "What is" section to the "Why you should care" 
section. It's not strictly necessary, but I like some kind of transition 
between sections.

It does add a few pixels of vertical space, but this is something we 
should look at from a higher level. There are many elements that take a 
lot of vertical space currently, so I'd like to keep the discussion on 
the functional level instead of going into the details of scale or 
pixels. We can make CSS tweaks later on as well if a certain vertical 
height is a requirement.

>> === Unify mobile development ===
>>
>> AeroGear provides flexible and extensible libraries to simplify mobile
>> development across platforms and cut common repetitive infrastructure
>> tasks. Integrate with the most exotic of endpoints.
>> [[ Get started >> ]]
> Where would this link go? We have multiple paths for getting started, thus, the platform buttons at the top.

To "Get the gear" or a page that is a little bit more in between a 
download page and a first run tutorial (I don't think this exists yet, 
but I'm happy to take that on as well).

>> === Simple API ===
>>
>> Talking to [[ RESTful ]] (1) backends couldn't be easier. We've
>> abstracted all of the plumbing into a simple programmatic API for doing
>> [[ CRUD ]] (2) operations and paginating large amounts of data.
>> [[ Browse API documentation >> ]]
> Which set of API docs? Each platform has their own, again, we have the buttons at the top.

This goes to the API Docs page that's already in present in the top 
menu. There can be more entry points to the same thing. Maybe it's a 
filler, but it's good for consistency to let every paragraph be followed 
by a link. I'm open to any other links if you can think of something better.

Thanks,

Hylke

>> === Mobility and security, both ===
>>
>> Integrate with your existing enterprise environment. AeroGear provides
>> Two-Factor Authentication and One-Time-Password features to improve your
>> application's security.
>> [[ Learn about AeroGear Security >> ]]
>>
>> === Easy server routing ===
>>
>> Define HTTP routes  with a simple Java Internal [[ Domain-Specific
>> Language ]] (3). The perfect fit for client-heavy applications where you
>> have very few entry points and delegate logic to the client tiers.
>> [[ Learn about AeroGear Controller >> ]]
>>
> I will leave security and controller comments to Bruno and Dan. These changes would also probably require imagery changes as well.
>> ------------------------------------------------------------
>> (1) http://en.wikipedia.org/wiki/RESTful
>> (2) http://en.wikipedia.org/wiki/Create,_read,_update_and_delete
>> (3) http://en.wikipedia.org/wiki/Domain-specific_language
>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev