[webteam] progress

[Adam Nemeth]

Hi all,

First I'm awfully sorry that I couldn't be there at tuesday... there
was a sudden important meeting, and I wasn't able to get into my
computer.

On 9/13/07, Peter Saint-Andre <stpeter at stpeter.im> wrote:
> 2. Created some content pages, for instance:
>
> http://stage.jabber.org/what-is-jabber
>

Well, I personally think that this page needs some more work :/ I
don't have heatmap analysis of course - btw: could we insert a code
for such on current jabber.org? - but for me the answer isn't
"Download a client" for "what is jabber?", even if I know that there's
some text "up there". It just feels to me: "they want me to download
something again... errgh..must be a virus". Jabber works on web too
anyway.

But a bulletlist is a good solution, just not this way I feel.

(UPPERCASE is bold, I'm sorry if it's disturbing, I just want to show
that it should stand out)

"Jabber is an
  * INSTANT MESSAGING SOLUTION, which is
  * OPEN for everyone,
  * SECUREd by industry leading standards,
  * SPAM-FREE as it can be, and
  * DECENTRALIZED LIKE E-MAIL, so you can host one for your company.

With Jabber you can:

  * Use a CLIENT OF YOUR CHOICE on _desktop_, _web_, _mobile_ - there
are more than 100 of them!
  * CHAT, TALK, GET TO KNOW other jabber users, and even
  * STAY IN TOUCH with your contacts who still using MSN,
Yahoo......... (continue)
  * CREATE YOUR OWN _corporate_, _organizational_, _community_  IM
NETWORK with free softwares, or different commercial vendors, and run
your own service
  * DEVELOP your own _IM-based_ and _collaborative_ applications by
using free code libraries for more than 15 platforms (including Java,
.NET, Windows/UNIX/Mac)

For more detailed information read... or go to the _forums_."

At the last two points, the links would go to case studies.

Java and .NET are emphasized because currently they're the two leading
enterprise platforms, and business workflow integration with IM makes
sense.


> http://stage.jabber.org/technology-overview
>

First: emphasize(bold), and use less text - I feel it's too vague for
web, but again we would have to get measures - other IM networks,
popular(!) free softwares (you'd never know how a good homepage would
make a foss project stand out!)

("vagueity" of text is usually measured by word count, wc, not
characters nor lines - just paste homepages to a cat | wc -w  for a
terminal)

Second: Although it's a fairly good marketing text, it does not give
me a technology overview. Like: I do not get that obvious information
on how this technology works ("like e-mail"), there's no architectural
diagram (I'll try to draw one), etc.

> http://stage.jabber.org/technology-detail
>

I feel it's like a "download-in-pdf" style documentation - it would
need again emphasizing, and diagrams - but it couldn't be used for
give an overview!

> And more:
>
> http://stage.jabber.org/quickstart
>

I wouldn't emphasize download this much - I know mac users don't fear
virus that much, nor compiling and binary incompatibility, not to
mention corporate policies (usually downloading exe is forbidden,
installing (registry) is forbidden) in a corporate environment!), but
these ARE serious issues on other platforms - exactly that's why
there's an uptide for web-applications and webservices.

I feel a wizard would fit better, or we should emphasize open networks
or something like that - honestly I feel I wouldn't install a software
just by curiosity after this tutorial :(

> http://stage.jabber.org/why-use-jabber
>

I feel this *should* be different for every audience!


By The Way: it was mentioned tuesday that we discourage the word
"end-users" as an explicit audience. I thought we could rename them
silently to "everyone", while still thinking of them as the end users
audience. What do you think?

(Or we could use "begginers", if it fits better)

Also it's a problem to create an *emphasized* audience-based
navigation. I came up with using that upper white line, and use color
repetition (like have a blue jabber logo for organizations, etc?).
I'll attach a mockup, and appreciate your feedback.

> Feedback is welcome. :)

It's mine... If it was a bit negative, I wasn't mean to: good
solutions shouldn't be changed, but worse ones should, that's why I'd
concentrate on those.

>
>
>


-- 
Aadaam <aadaam at gmail.com>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: audience_selector.png
Type: image/png
Size: 201070 bytes
Desc: not available
Url : http://mail.jabber.org/pipermail/webteam/attachments/20070913/26f3d184/attachment-0001.png