in reply to Documentation App

If you care to invest the time, there are some content management systems available apart from Wikis, for example the Everything Engine and Slashcode. Both have their own problems and advantages, and you also need to understand how technical your users will be. Wiki syntax has the advantage that "normal text" as typed on a typewriter will already magically render "well enough". If your customers prefer to enter text in a LaTeX style notation or HTML or whatever else, you might want to use some engine that already has plugins, like CGI::Wiki.

There are other considerations, for example, the Everything Engine runs all code from the database, which has been discussed here, and which has a set of advantages and problems all of its own.

There is also Bricolage and ??? the content management of perl.org, both of which I have absolutely no experience with.

Replies are listed 'Best First'.
Re^2: Documentation App
by Jaap (Curate) on Jul 14, 2004 at 08:58 UTC
    Most colleagues prefer to use wiki-markup language because it is so damn fast to write in, (untill you want to do something it can't) but for the die hards it might be good to use pure html too. Customers will not write our documentation unfortunately, they will just read it (unless you mean MY customers, which are my colleagues ;-). I am a bit worried about using a full CMS like the everything engine or one of the 3000 other ones. THey might be too heavy-weight for this.