Hi Justin, A simplest solution maybe just by using a wiki, I know quite a few projects use wiki for their documentation but maybe not for projects as big as yours. Eg. Tavi wiki, tiki, phpwiki.
Another better out-of-the-box solution is maybe plone. (plone.org). It's a portal skin built on Zope's Content Management Framework. It might be hard to customize to a exact look that you may want. It does provide those functionalities that you wanted eg login, user area, i18n, however it is based on Zope's own object DB (ZODB), it might be possible to emulate that onto PostgreSQL I'm not sure. But Zope can connect to PGSQL for sure. I think there are products for collaborative books, etc. Well, that's my suggestion. Cheers, Rex. > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:cms-list-admin@;cms-list.org] On > Behalf Of Justin Clift > Sent: Wednesday, 30 October 2002 12:24 AM > To: CMS Mailing List > Subject: [cms-list] Arrrgh... which system to use? > > Hi all, > > Trying to figure out if what we need is *really* a CMS or not, but it's > kind of hard to know, being new to the field and having extremely > limited time to learn about it in any other way than "hands on". Am > hoping people on the list can give further guidance in this matter, as > it's pretty new to me. > > Looking for a system that lets multiple people register on a site, then > collaboratively co-author manuals/guides/documents/etc. > > For example, with PostgreSQL we have a really strong following of > volunteers and users, and they're almost all web-savvy, and they're > spread around an extremely diverse array of operating systems, > environments, etc. > > We're looking for some way of allowing the members of the PostgreSQL > community to co-operatively develop things like a "PostgreSQL Tuning > Guide" and other such documents in an online fashion, preferably using > common technologies (i.e. Mozilla as a front end, etc). > > There are some technical specs that constrain what we're looking for > too: > > - If it uses a database then it has to work with PostgreSQL > - The server side stuff we run for the postgresql.org servers is all > unix based, predominately FreeBSD and it would have to run with that. > - Must have the capability to support multiple languages, whether > through unicode or some other means. Translators are around to do the > needed stuff, but it doesn't help if the capability doesn't exist to > cater to them. > > Open Source is definitely preferable, and being a community effort we're > extremely cost sensitive. > > Assuming we find something that works well for everyone, there's an > extremely good chance that other very large Open Source projects will > also adopt the solution. > > Is what we're looking for a CMS? If so, any recommendations? > > Sorry for the unusual email, it's just that I can describe what we need, > but not sure where to look and there are *so many* different systems > around with the label of CMS that it's hard to figure it out. > > Regards and best wishes, > > Justin Clift > > -- > "My grandfather once told me that there are two kinds of people: those > who work and those who take the credit. He told me to try to be in the > first group; there was less competition there." > - Indira Gandhi > -- > http://cms-list.org/ > trim your replies for good karma. -- http://cms-list.org/ trim your replies for good karma.
