To add my two cents. Avoid the book module. Everything it does can
be done with a combination of cck, cck node reference and views.
Doing it that way is much better supported.
We have a site with well over a thousand book pages and as a result
have had major trouble exporting, importing or even using modules like
deploy. If you use the combo mentioned about you can avoid those
problems and get much better community support.
--
Travis Wooley
On Wed, 15 Sep 2010, Scott Holmes wrote:Scott,
> I doubt you'll find any structural difference between a "Page" and a "Book
> Page" as both are nodes. The default behaviour can be customized. By
> default the only real difference in behaviour is that a book page displays
> links to the next/previous pages in a book. A book is merely a collection
> of nodes assigned to a book. If you have the book module installed it is
> possible to assign a preexisting page to a book.
Thank you. I have to think how the pages of the current site can best be
organized within Drupal. And what capabilities might be worth adding.