On Wednesday 14 January 2009 11:37, Clayton wrote: > There is no reason we can't have both in the same Wiki...
Clayton, in my above mail I tried to explain you exactly this reason. It may be simply called usability. For end users (as me) it is very frustrating to search for program documentation and to get hundreds of project related results which do not help to solve my problem. > a > free-for-all playground for development projects, and a more > structured section for end users. how do you want to separate the two? A wiki is an entity. To separate the two "sections" as you call them you would have to put in much more work than for the maintenance of two separate wikis. Not necessarily more administrative work but more educative work, to make people follow naming conventions, to explain them how to confine search to one of the sections and similar. Don't get me wrong: for starting it's ok to have anything in one place. But when usability (or performance) starts to get relevant, then "one wiki one purpose" will be the far better solution. At least for me, the end user. With documentation it's similar as with software: beta releases should not make it to the average end user, the product should be perceived as consistent as possible. And the wiki is full of inconsistencies, trials and errors just because of it's nature as playground as you called it yourself. For the germanophone community an end user wiki (ooowiki.de) has been raised several years ago, and when needing a solution I always first consult that wiki as it returns far superior results (if the topic is covered there). Nino --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
