Before we go any further about what to do with this topic specifically, I think it is important we identify what Confluence is capable of doing and then plan from there.
It doesn't seem like a document can have multiple parents, however is it possible to build navigation / child pages based on labels? Just looking at the wiki describing Confluence, I see that they group documentation based on version number at the dashboard. ( http://confluence.atlassian.com/dashboard.action ) I don't know if they recommend it as a best practice, but it speaks to me. I am not fluent in Confluence, so I would be interested in hearing thoughts. A- On 7/20/09 12:54 PM, "Marvin Addison" <[email protected]> wrote: > Moving this to cas-dev since it's really about documentation at this point. > >>> I added a "Services Management" section to >>> http://www.ja-sig.org/wiki/display/CASUM/Clustering+CAS. I'd like to >> The trick is that this information relates to both Service Management and >> Clustering >> ... >> Perhaps the Cluster CAS section should be broken out into the different >> pieces that need cluster consideration? > > I like that suggestion. I noted the Clustering CAS page is pretty > dense in some areas, and noticeably silent (e.g. JPA ticket registry) > in others. It could benefit from some sort of reorganization. I > think adding clustering considerations to the pages about specific > topics, e.g. TicketRegistry, Services Management, would help keep > things on topic. The clustering page could then summarize all > possible considerations for clustering and link to the topic-specific > pages for details and configuration guidance. > > Thoughts? > > M -- Andrew Feller, Business System Programmer LSU University Information Services 200 Frey Computing Services Center Baton Rouge, LA 70803 Office: 225.578.3737 Fax: 225.578.6400 -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
