I'm just about to setup our documentation and have been having a play around with Documents. What I'd like to know is Are there any advantages of multiple books that outweigh the complexity of maintaining them?
Thanks.
Latest Tweets
On my way to #drupalcon with 3000 other geeks, hoping to fill my brain with useful Drupal goodness!
RT @pythondj #Drupal Geeks On a Train: @Groupanizer's CEO Tom Metzger is a Man on a Mission http://t.co/Jz9X8OckXK #dcstories #DrupalCon
Follow Us
Contact
Main Phone: +1 604 451-SING (7464)
Fax: +1 604 451-7465
By mail:
Groupanizer
3073 E 21st Ave
Vancouver, BC V5M 2W6
Canada
Business hours:
Mon-Fri 7:30am-5pm, Pacific Time Zone
There are some oddities about what can be included as part of a book and what can't. I played around with the hierarchies and eventually decided that having one book called "Documents" and adding other documents as child pages each with its own child pages was the best way to go for me. That's because a "book" can't be included within another book: books can have child pages, but they can't have "child books." What I was after was to have all of the "books" show up when someone clicked "document" and I achieved that, so I'm no longer quibbling over silly terminology.
Cindy
Director, Pittsburgh Threshold Choir
Pittsburgh, PA, USA
http://ptc.groupanizer.com
I have 2 books setup - one for Documents (as per Cindy's comment above) and one for FAQ. Both are very useful in their own ways.
I think multiple books are good if you have well defined reasons for splitting the information into multiple areas. If you don't need to have it separate, then you and your members will find it easier to keep in one place.
Antony Currington
Musical Director :: Harbour Capital Chorus
Email :: acurrington@paradise.net.nz
Wellington, New Zealand