Yep, that's my recipe too,except for icw, which might seem like preference.
The book module provides the important "log" function that contains the meta discussion associated with updating content. I might argue that the "log" could ideally be configurable on a per content type basis, so you could do it for a page, story, or something else.
You could really get wiki-like if you considered a "multi-node" display module that showed all the node content associated with a particular book page "parent", with edit links for each of them on the pages.
Dave
-----Original Message-----
From: development-bounces(a)drupal.org [mailto:development-bounces@drupal.org] On Behalf Of Bèr Kessels
Sent: Wednesday, August 23, 2006 12:18 PM
To: development(a)drupal.org
Subject: Re: [development] Wiki module
Op woensdag 23 augustus 2006 19:24, schreef Neil Drumm:
> I recently helped set up a wiki for one of our client sites. We used:
> - CCK (4.7)
> - TinyMCE
> - freelinking
> - input_format_restrictions - a formapi hack module that lets you
> define the default and available input formats for each node type [1].
> I plan on making a patch for core for this, but haven't had time. The
> first step, in case anyone wants it, is being able to set the default
> and available input formats when calling the function which generates
> that form widget.
Here is my recipe:
book module (It's great to be able to actually structure a wiki!) node_privacy_by_role (we needed three groups that could not edit or see eachothers content. If you need more OG configured for books will be a good
option)
freelinking
markdown icw with a properly configured input format. (My client found markdown far more "natural" then HTML or WikiSyntax) inline module upload module (icw inline provides a simple way to include images)
Bèr
