On Sun, May 20, 2012 at 3:05 PM, Horst Gutmann <[email protected]> wrote:

> On Sat, May 19, 2012 at 6:06 PM, Giovanni Collazo <[email protected]>
> wrote:
> > Hi,
> >
> > So, I spend a few hours working on the re-design following Idan's
> > Guidelines. Any feedback and further direction from the core team would
> be
> > greatly appreciated.
> >
> > G.
> >
>
> Hi :-)
>
> Looks nice! A few points though:
>
> * Do we really need the pony?
>
> * IMO the "Meet Django" section might be better one step up since the
> line "Django makes it easier..." might not be enough to quickly
> explain what Django actually is.
>
> * "Meet Django" and "The Django Framework" sections have more or less
> the same objective and should IMO be combined to make it possible to
> put the community section slightly higher in the structure.
>
> * Regarding prominent actions: Perhaps you could place some action
> buttons where the pony is right now. Like something for developers,
> something for novices and something for project managers.
>

I think removing the Pony for an action item will clutter the space. I like
the pony, but if it's decided to not go with it, putting action items in
there will clutter it in my opinion.



>
> * For the quickstart I'm personally not really a fan of lightboxes.
> They should provide supplementary information, not primary info.
>
> Best regards,
> Horst
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/django-developers?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Reply via email to