[webteam] radical simplicity

[Artur Hefczyc]

Hi,

> In particular, we talked about the possibility of scrapping Drupal
> altogether and simply using XHTML and server-side includes, or at most
> XML+XSLT, to generate the jabber.org website. This is what we do for  
> the
> xmpp.org site and we never have a problem there.

The only people who don't make mistakes are those who do nothing.
I think similar thing applies to computer programs:
The only programs without bugs are those which don't do anything.

So going back to plain (X)HTML would be like going back to program which
does nothing and is error-less.

> Is the jabber.org really all *that* different or special that it  
> requires a full CMS?

This is a good question and I think the answer is *yes*.

xmpp.org is for *publishing* standards. It is more like a static  
content website.
A website with pretty static documents (updated from time to time). A  
website
very boring for most mortals who don't need to know XMPP specification  
or
details of XEPs.
I would say xmpp.org is in some way passive website where people look to
get some information only.

jabber.org is for users. People who want to use Jabber (instead of  
implementing it).
It has a chance to be live where people not only get information but  
also can share stuff.
Developers can submit their XMPP projects, update project details,  
users can
exchange opinion, share some ideas which might be not a technical  
specification
but rather thought from the user point of view.
It could keep list of running XMPP services with description. It could  
be maintained by
service administrator the same way software list is maintained by  
developers.
Well, it is not like this, right now but note that this is still quite  
fresh thing.
All these stuff are distributed over different websites right now:
www.jabber.org
jabberforum.org
planet.jabber.org
and maybe something else.
I would be good to combine them all in a single service under www.jabber.org 
.

> Your thoughts are welcome. :)

That would be simply step back. Sacrifice functionality to minimize  
chance for
human mistakes?

Artur
-- 
Artur Hefczyc
http://www.tigase.org/
http://artur.hefczyc.net/