[webteam] drupal structure mindmap

[Adam Nemeth]

Hi,

Let me argue against the concept drawn in this mindmap. I know that
the winner idea is always whose who actually works, but I've been on
the web market for years, and it haven't changed as much as an
outsider ("web 2.0") would think.

We already agreed that we'll use path / audience-based navigation,
because we have several audiences with different needs. It's a theory,
but it can be supoorted by the statistics (we'll have to monitor those
much more after the new site starts!).

Therefore, I do not want an end-user to know what is a XEP, since it's
too complicated against "download Windows Live Messenger
<link>here</link>". jabber.org [ejabberd]server statistics is again
one thing that is absolutely unnecessary for end-user experience. (I
know there could be found an argument that it is, but it's hard to
convince me That it should be a main-menu feature.)

"mission" is again not a main menu feature: it's our own problem, not
the end users', although we should clearly present it in every point
of the site, every hour, after waking up, while brushing teeth etc..
:) But it's not something a user would care by himself.

I think I already mentioned what an end-user needs:
- Forum / Chatroom (support)
- "Download jabber here" (->Client list)
- "Register jabber here" (->Server list + Client list)
- Wazdat jabber thin? ;)
- Clients list (ok, server list too)

Then come the developers (deeper understanding; yup:
- XEPs,
- libraries,
- rfcs,
- mashups,
- planet jabber,
- blogs,
- mailing lists,
- jdev at conference,
- probably servers, etc)

The corporations (Did you know that EIM is the most popular social tool? Check

http://tinyurl.com/3bt4g7

) are another thing; probably I would connect this with sysadmins
("those people inside a corporation who actually make things happen
after managers have seen jabber.org; or they show them it:)"). They'd
surely need the emphasis of
- need of collaboration,
- some success stories,
- server vendors,
etc, along with
- client tools,
but less emphasis on the public infrastructure.

So I think it's needed to think along this way. I know both of us have
the largest knowledge of what developers need (therefore we think of
xeps, missions, mailing lists, etc), and we want to convince end
users, since we think we are one (although they have much less
knowledge of the technology world and care much-much-much less about
our mission of open networks and so on), but the real world is much
more differentiated.


On 8/3/07, Robert Martinez <mail at mray.de> wrote:
> I've just uploaded my mindmap:
> http://wiki.jabber.org/index.php/Jabber.org_relaunch# (at the bottom again)
> The purpose of the mindmap is to provide an overview, but it is not
> finished yet.
>
> One big question that remains open is: shoudl we make XEPs and features
> taxonomy or nodes?
> (fot the ones not so familiar with drupal: taxonomy = "tag", while
> "node" is a customizable page entry)
>
> pro taxonomy:
> + easy to filter nodes by taxonomy (not so easy with node references)
> + uncomplicated when we want a multi language page
> - no big options to provide additional information to features and XEPs
>
> arguments for node:
> + we'll  have complete nodes to describe and handle XEPs and features
> (attach images af multiple fields etc..)
> - when we have a multi language we run into serious problems (assign
> german, italian and english XEPs nodes to a client node??)
> - views module does not seem to be able to create filtered lists by
> refereced nodes
>
> Please comment on it - since having a more complete overview will ease
> the future work on jabber.org for everyone.
>


-- 
Aadaam <aadaam at gmail.com>