[JDEV] Documentation Backend & Target Markets

[Adam Theo]

I'm now beginning to re-do some of the documentation on the jabber.org 
site. I'm wanting to know the backend for all of it, including the 
www.jabber.org/docs page itself. stpeter & temas: could i get access to 
whatever backend it does run on?

Also, to start my documentation spree, what target markets could the 
Jabber technology tackle? Here's what I have:

* End User IM - like AIM, ICQ, etc. For both teenage and corporate users.
* Middleware/Data Routing - Like what DotGNU is using Jabber for now. An 
alternative/replacement to HTTP potentially.
* Chat system for softwares - Like what I am trying to get FreeCiv into. 
An alternative to ad-hoc, home-grown protocols for specific applications.
* Service providers - such as ISPs and office solutions. Used for 
inter-worker communication. As an alternative to MSN and AIM offerings 
for the corporate setting.
* Groupware/Collaborration - Crude yet in Jabber, but will someday be a 
contender. Includes group text editing, whiteboarding, and calendaring. 
Alternative to Groove and Magi (although hopefully work with them).

-- 
     /\  Adam Theo, Age 23, Tallahassee FL USA
    //\\   Email & Jabber: theo at theoretic.com
   //  \\  (Boycotting AOL, therefore no AIM or ICQ)
=//====\\=  Theoretic Solutions: http://www.theoretic.com
//  ||  \\     "Bringing Ideas Together"
     ||      Jabber Protocol: http://www.jabber.org
     ||         "The Coolest IM on the Planet"
     ||  "A Free-Market Socialist Patriotic American
     ||      Buddhist Political Philosopher."