In article <[EMAIL PROTECTED]>, Bart van Bragt <[EMAIL PROTECTED]> wrote:
> Peter Saint-Andre wrote: > > What do you have in mind for user-friendly content changes on jabber.org? > > Not sure because IMO jabber.org is fairly OK as a developers portal. But > this is the first sentence of the 'What is Jabber' page: > > "Jabber is a set of streaming XML protocols and technologies that enable > any two entities on the Internet to exchange messages, presence, and > other structured information in close to real time." And the second sentence reads: "The first Jabber application is an instant messaging (IM) network that offers functionality similar to legacy IM services such as AIM, ICQ, MSN, and Yahoo." Or shall we just assume that no one on this planet reads past the first sentence of any web page? > Imagine what happens if your grandmother reads that ;) Or what happens > if your grandmother figures out that she can talk to her bridge parter > through Jabber if she installs a client. To choose a client she'll go to: > http://www.jabber.org/software/clients.php Yes, it would help to have a recommended short list of clients, such as I did for the IETF chat pages: http://www.xmpp.org/ietf-chat.html > But for the 'What is Jabber' page it would be nice if it would start > with some plain language that tells the reader that Jabber is a great > Instant Messaging system with great clients like Psi and Pandiom (or > whatever) and state some advantages for your average user. Being based > on XML is not one of those advantages ;) Maybe a 'quickstart' page for > endusers is a nice intermediate solution until the community site is > properly up and running? Sure, I'll put something together. /psa _______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mail.jabber.org/mailman/listinfo/jdev
