[support] current wiki tools in drupal

Ari Davidow aridavidow at gmail.com
Fri Mar 7 21:45:10 UTC 2008


Good points. Roetzi's sample drupal page (http://test.tschannen.net/ ) makes
a point of including diff and recent changes, I presume for exactly the
reason you describe, as well as node lock (two or more people simultaneously
editing?), talk (for the metadiscussion), along with pearwiki filter and
wikitools.

ari

On Fri, Mar 7, 2008 at 3:27 PM, Shai Gluskin <shai at content2zero.com> wrote:

> Ari and folks,
>
> To me the core functionalities of a Wiki are:
> 1. Versioning - each change is preserved
> 2. Diff - users can compare versions
> 3. Multiple user edit privileges to the same text (e.g. "node" in Drupal
> speak).
>
> So lets apply that to Drupal.
> 1. Versioning is built in. Just make sure on the content-type edit page
> under workflow that revisions is turned on.
>
> 2. Diff - you need a module for that. Fortunately the diff module<http://drupal.org/project/diff>is excellent and well developed/maintained.
>
> 3. The editing privileges you should be able to handle without adding any
> modules -- as long as the Wiki pages on your site get their own content-type
> - which you can do even without CCK (as long as you don't add any fields).
>
> Starting with D5 you can use the Book module for nodes that have content
> types other than book. This is awesome. You do have to create one node for
> each book that was created using the book content-type. But then any node
> can be assigned to it via an "outline" tab which appears. However, this
> relates to the navigation/page organization you want to provide for folks --
> and there are other solutions to using the Book module.
>
> I do find there is a lot of confusion out there about what a Wiki is. I
> know a lot of teachers use Wikispaces.com simply as a place to build web
> pages, for themselves and for their students, with no intention of
> collaborative writing, manual creation, multiple editors for the same page,
> etc. My feeling is those pages aren't Wikis.
>
> Shai
>
>
> On 3/7/08, Ari Davidow <aridavidow at gmail.com> wrote:
>
> > We're beginning to describe a Drupal project that we feel is "wiki-ish"
> > and I am thoroughly confused as to what would be needed to implement a
> > "wiki" using drupal. It looks like wikitools provides some filters to
> > translate between wiki markup and regular html, but for our purposes, that
> > is the piece we care about least. (We intend to use tinyMCE or equivalent
> > for markup--the users of this project will not be any happier with wiki
> > markup than with html.)
> >
> > So, what makes a page a wiki? We are thinking of a few primary elements:
> >
> > 1. The ability of any registered user to edit the page in a browser.
> > (Note: Any registered Drupal user with appropriate permissions can do this
> > with any Drupal page, as well.)
> >
> > 2. The ability to view the page's history and to roll back changes
> > easily. (This may also be built into Drupal?)
> >
> > 3. The ability to create a new, blank page by creating a link to it.
> >
> > Are we really just talking about a standard Drupal book? When other
> > people say 'wiki,' to what more are they referring (or is the "what more"
> > wiki markup language?)
> >
> > ari
> >
> >
> > --
> > [ Drupal support list | http://lists.drupal.org/ ]
> >
>
>
> --
> [ Drupal support list | http://lists.drupal.org/ ]
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/support/attachments/20080307/0014acfe/attachment-0001.htm 


More information about the support mailing list