Actually, I wasn't suggesting that volunteers write everything from scratch, but that you provide the core, and the selected people could be "editors" as it were.
See http://www.virtualmin.com/documentation for an example. They (company) wrote all the initial documentation using Dokuwiki. Now, users are allowed to add or edit items, etc.
It's very easy to get change notifications, so for example, when I added a section there on custom user email notifications, they immediately knew about it, and filled in some of the blanks in what I knew about the topic, etc. (This actually happened over about a week+ span).
I think it's possible to generate a independent downloadable document from the wiki too. I'm not sure if Dokuwiki can do that but I think TWiki can (or one of the others). That would give you both worlds.
So, definitely, I expect the authoritative voice in the documentation would be Pleco.
In fact, you don't have to allow open user editing to make the wiki useful since it would be an online up to date version of the manual anyways. I was trying to save you some time.
See http://www.virtualmin.com/documentation for an example. They (company) wrote all the initial documentation using Dokuwiki. Now, users are allowed to add or edit items, etc.
It's very easy to get change notifications, so for example, when I added a section there on custom user email notifications, they immediately knew about it, and filled in some of the blanks in what I knew about the topic, etc. (This actually happened over about a week+ span).
I think it's possible to generate a independent downloadable document from the wiki too. I'm not sure if Dokuwiki can do that but I think TWiki can (or one of the others). That would give you both worlds.
So, definitely, I expect the authoritative voice in the documentation would be Pleco.
In fact, you don't have to allow open user editing to make the wiki useful since it would be an online up to date version of the manual anyways. I was trying to save you some time.