[dokuwiki] Re: Best practices of multiple documentation releases

  • From: Andreas Gohr <andi@xxxxxxxxxxxxxx>
  • To: dokuwiki@xxxxxxxxxxxxx
  • Date: Mon, 02 Jul 2007 16:58:57 +0200

chris writes:

YC Chan wrote:
Best practices of multiple documentation releases *********************************************************

WIKIs are traditionally used for 'living' documents i.e. ones under constant change. When a version is finalised and need to be archived
for later reference, the 'usual' WIKI practice is to build a PDF
version and archive it as an attached document. It becomes difficult
for searching and comparison, especially when you have multiple versions.

So much so for the usual treatment. Maybe the latest versions of
commercial WIKIs have a better way: if you know of any, please keep
everybody informed!

I believe Trac has been working on functionality to make SVN its wiki backend. Thus allowing for this type of thing.

AFAIK Trac does not store the Wiki data in SVN, but uses MySQL or SQLite.

To answer the intial question: I assume that the documentation of a released product won't change anymore, so why not just move the whole Wiki install to an archive and copy the contents to a new "current" wiki?

Andi


--
DokuWiki mailing list - more info at
http://wiki.splitbrain.org/wiki:mailinglist

Other related posts: