<p>To add my two cents. Avoid the book module. Everything it does can<br>be done with a combination of cck, cck node reference and views.<br>Doing it that way is much better supported.</p>
<p>We have a site with well over a thousand book pages and as a result<br>have had major trouble exporting, importing or even using modules like<br>deploy. If you use the combo mentioned about you can avoid those<br>problems and get much better community support.<br clear="all">
<br>--<br>Travis Wooley<br><br><br></p>
<div class="gmail_quote">On Wed, Sep 15, 2010 at 9:33 PM, Rich Shepard <span dir="ltr"><<a href="mailto:rshepard@appl-ecosys.com">rshepard@appl-ecosys.com</a>></span> wrote:<br>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">
<div class="im">On Wed, 15 Sep 2010, Scott Holmes wrote:<br><br>> I doubt you'll find any structural difference between a "Page" and a "Book<br>> Page" as both are nodes. The default behaviour can be customized. By<br>
> default the only real difference in behaviour is that a book page displays<br>> links to the next/previous pages in a book. A book is merely a collection<br>> of nodes assigned to a book. If you have the book module installed it is<br>
> possible to assign a preexisting page to a book.<br><br></div>Scott,<br><br> Thank you. I have to think how the pages of the current site can best be<br>organized within Drupal. And what capabilities might be worth adding.<br>
<div>
<div></div>
<div class="h5"><br>Rich<br><br>--<br>[ Drupal support list | <a href="http://lists.drupal.org/" target="_blank">http://lists.drupal.org/</a> ]<br></div></div></blockquote></div><br>