We are moving all our (limited and badly organized) documentation to a wiki. Anyone got any examples/pointers to a hierarchy that made logical sense? We are hoping to move everything from topology to application specific notes in to the wiki. Given the size of this task, I only want to do this once:) Thanks for any reco's! jlc
Hierarchies are as diverse and personal as they come. What is more important is to have your site be searchable. To that end you might invest in adding search tags to each document. So that you have access to them all in a flat way as well as the hierarchy. --Glenn 2009/1/23 Joseph L. Casale <JCasale at activenetwerx.com>:> We are moving all our (limited and badly organized) documentation to a wiki. > Anyone got any examples/pointers to a hierarchy that made logical sense? We > are hoping to move everything from topology to application specific notes in > to the wiki. Given the size of this task, I only want to do this once:) > > Thanks for any reco's! > jlc > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos >-- See my blog at http://snap-happy3216.blogspot.com
In a wiki, you are typically shooting for a flat structure, and the links in the pages organically make a structure. As already said, searching is the key. In the past, with Word docs or even text files, you needed to impose a hierarchy because it made things easier to find. Now you just need to search. You might want to take a look at wikipatterns.com for some useful ideas on how to run a wiki. On Thu, Jan 22, 2009 at 9:48 AM, Joseph L. Casale <JCasale at activenetwerx.com> wrote:> We are moving all our (limited and badly organized) documentation to a wiki. > Anyone got any examples/pointers to a hierarchy that made logical sense? We > are hoping to move everything from topology to application specific notes in > to the wiki. Given the size of this task, I only want to do this once:) > > Thanks for any reco's! > jlc >