I've seen interesting web-based collaborative environment (which I definetelly will use for our project documentation - just do not know when to do it...). It's called Wiki and has many free clones.

I am interested in Wiki clone called TWiki, because TWiki is rather advanced (authentication users by groups, advanced page formatting, version control), nice active development group, and more than hundred instalations).

See TWiki in action   and   TWiki feature overview slide-show presentation.

There are many different Wiki clones, I recall something like DolphineWiki or ModWiki, which is static (pages generated on demand), much simpler than TWiki.

Wiki is much simpler (IMHO) to use for plain users than HTML for text formatting, and WikiWords will link to page with the same name(explained on website). Every member of Wiki community can update these pages, great for documentation. TWiki will send you email that page you care about (and subscribed for) was changed. Version control will allow some admin users to undo changes if needed. TWiki has also "categories", so you can change some set of status fields - so you can use it i.e. for bug tracking.

However, they do not have XP and voting... :-(

You have also full source code, so it might give you a nice headstart when creating MonkWiki for your docs... ;-)

Does somebody around here have experience with Wiki? I know Wiki is kind of "competitor" with Everything Engine in field of free web-based collaboration tools, so I hope it is not blasphemy to mention Wiki here...;-)

Difference is: WikiPage is like thread in PM. Everybody can update any page, also text of others (Wiki does not support strict "ownership" of node as PM does. So there is smaller amount of pages, and links can by improved in time. Can you image all nodes explaining why use strict linked together? Easier to search. But, when you just adding text to the end of the page, it is less dynamic than threads in PM. Not having to worry about XP is good - and not having XP is bad. So, is better for documentation, but less fun for comunity like PerlMonks.

As somebody said here: Forget about XP, remember the experience...

BTW, Wiki-Wiki is "quick" in Hawai-an language.

pmas
To make errors is human. But to make million errors per second, you need a computer.

In reply to Re: HTML documentation system - design and planning by pmas
in thread HTML documentation system - design and planning by John M. Dlugosz

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.