[Grok-dev] Re: Suggested site structure
kevin at bud.ca
Tue May 15 23:33:40 EDT 2007
On May 15, 2007, at 4:24 AM, Martijn Faassen wrote:
> Sebastian Ware wrote:
>> Suggested site structure using the 4 E model (Excite> Educate>
>> Empower> Engage).
>> I also suggest having the content mature over time.
Rails and Plone both present a 4E-ish face on their web sites -
rubyonrails.org and plone.org have something like:
Excite > Get > Educate > Engage
It's a powerful way of presenting information, splitting it up into
sections, with a users involvement with the system being categorized
from left to right. I tried to develop my organizations home page
differently since I didn't want it to "look like plone.org" but in
the end I came back to that kind of layout because I couldn't come up
with anything else that felt satisfactory.
> * when developing I look for a documentation section. Right now
> documentation is split up between Learn and Develop. Can we present
> all documentation in one place somehow too with this?
+1 on uniting documentation within one section, however I would make
distinction/exception between documentation designed for someone who
is wants to build applications for Grok and someone who wishes to
develop core Grok itself - so that we don't confuse a Grok Developer
with a Developer of Grok :)
> * I don't see a 'download' section. In order to get the users to
> try things out, it needs to be obvious what to download and how to
> install it.
I like the idea of a full 1/4 section dedicated to "Get". This
doesn't really fit in with the 4E model, but the act of checking for
new releases, downloading the latest release, etc. is so common with
an open source application that it is really nice to have a dedicated
1/4 section for it. I like the phrase, "Get Plone" but "Get Grok" is
somewhat confusing because "get" and "grok" are both synonyms for "to
better understand". The phrase "Download" is nice and straightforward
More information about the Grok-dev