Merging Wikis

[Robert Impey]

Currently, there are two wikis associated with this project.

There's a Google Code one:

http://code.google.com/p/haddock-cms/w/list

and a MediaWiki based one at:

http://wiki.haddock-cms.com/

Originally, the MW based wiki was only used in-house at CLWD and the
Google Code one was meant for public consumption.

For a brief while, I thought that a division of wiki documentation for
the project along the lines of that of the Oedipus Decision Maker
would make sense:

http://groups.google.com/group/oedipus-decision-maker-discuss/browse_thread/thread/36f7555142b2eeb4

In this scheme, the MW wiki would just be for non-technical users and
the Google Code wiki is just for writing about the code.

I'm not sure that such a separation makes sense for a project like
Haddock CMS, which is aimed at admins. However, the project is also
aimed at non-technical writers and admins.

Bear in mind, there's quite a bit of technical stuff already on the MW
site, which I'm not going to move to the GC wiki any time soon.

What do you think is the best division?

[Saul Howard]

I think it is key to have documentation that aims at being as non-
technical as possible. Step by step install instructions that assumes
hardly any knowledge on the part of the user.

I think that the MediaWiki is the better wiki to use for this as just
the fact that a wiki is on Google Code makes it a little bit
technical.

But I'm not sure that we need two wikis - although maybe this is a
good idea to help us write such non-technical pages, by moving only
necessary content over to Media Wiki and doing most of our technical
writing on GC.