|
: 19 : 19 : 0 |
Part of the value of a redbook has always been the organization and flow of the material. The team writing the redbook would know the content they needed to produce and would provide an organization structure for how they would proceed through the material.
If there's a Lotus Domino Designer Wiki, it should have the same thought applied to it by the team before even publishing the Wiki to the general public. Yes, to begin with, almost every entry would be a *stub document, but at least it would provide the organization for material coming in.
Then as authors start to contribute content they can decide if it should go into one of the already defined topics, or split off from a subtopic. At the top level, I wouldn't allow users to add new main topics, but create a single branch for "additional user contributions" that could go wherever people wanted to take it and tree out from there.
This way, the major documentation areas would be surfaced clearly and provide a framework for all expected documentation in the Wiki. Perhaps it would still be necessary to convene Redbook teams for this very purpose: decide what the important topics and structure of the Wiki should be and get that published.
|