[documentation] [Fwd: [development] book module patch]

[Steven Peck]

I wish I'd seen this earlier.  To busy.

Currently the D.O. handbook is 5 'books'.  Each 'section' is a separate
book.  Unless someone snuck some forum nodes in it, it is all book type
nodes.  So most likley we'd convert them to separate books.
Reorganizing ONE book and part of another took me 40 hours over 5 days
back in Jan(?).

Unlike some, I move pages between 'books' often enough.  Your early use
case is a little limited.  'Re-organizing' technical manuals immediately
comes to mind.  Also at least two munincaplities use Drupal book module
for their city code manual and one of the long ago forum comments was
they saved money on a third party solution by the ease of
re-ordering/adding pages to various sections in Drupal books as code
changes were passed in council.  The assumption of books on a site being
unrelated is not broad enough, but I'm still reading the May comments
while I write this so may not be applicable anymore....

Book module is a powerful feature of Drupal  I see this as expanding
this feature and broadening it's usefulness to a wider audience.  I am
moved enough to actually setup a test site for HEAD this weekend which I
normally don't do until after the freeze.

Things to test against not currently seen, path module.  Lots of aliased
pages on d.o.

-sp

> -----Original Message-----
> From: documentation-bounces at drupal.org 
> [mailto:documentation-bounces at drupal.org] On Behalf Of Peter Wolanin
> Sent: Thursday, August 24, 2006 12:45 PM
> To: A list for documentation writers
> Subject: Re: [documentation] [Fwd: [development] book module patch]
> 
> The current intention (and, I hope, effect) is that a site like
> drupal.org would see no substantial difference after the update.  The
> goal is to substantially add functionality without breaking data or
> sites.   I invite people to test this, and included at that issue a
> script to generate book nodes to test the update path.
> 
> Here's what's new:
> 
> current "book" nodes will be converted into "book_page" nodes.
> 
> An additional content type "book" will be made available.  The "book"
> works much like a group in the OG module- nodes can be associated with
> it.  This makes organizing the pages associated with each book easier,
> since the select box to choose the parent node will only show the set
> of nodes associated with the same book.  The "book" node itself can
> display a license, list of authors, and a table of contents spanning
> all associated pages (and the preferred depth of TOC display is
> selectable when editing the "book").
> 
> book_page (and other) nodes can also be part of a hierarchy but
> independent of any book (book ID = 0).  All exising pages will be put
> in this category during the update, and the book nav block should work
> as before to use the title of the top-level page in the current
> hierarchy.
> 
> Users with the "outline books" permission will now be able to organize
> all pages in the book, or move a page and its children to a different
> book, even if they cannot edit a particular page.
> 
> For Drupal.org, I'd suggest converting all the current top-level pages
> into "book" nodes to take advantage of the additional features, but
> that's optional.
> 
> -Peter
> 
> On 8/24/06, Neil Drumm <drumm at delocalizedham.com> wrote:
> > This affects the book module quite a bit. I'd like to hear 
> how it wll
> > affect drupal.org.
> >
> > -------- Original Message --------
> > Subject: [development] book module patch
> > Date: Thu, 24 Aug 2006 12:02:28 -0400
> > From: Peter Wolanin <pwolanin at gmail.com>
> > Reply-To: development at drupal.org
> > To: development at drupal.org
> >
> > I have been working with Augustin (beginner) on a substantial patch
> > for the book module:
> >
> > http://drupal.org/node/65319
> >
> > Your review of this patch and comments would be highly 
> appreciated, as
> > well as your support for getting this RTBC within the next week.
> >
> > --
> > Neil Drumm
> > http://delocalizedham.com/
> > --
> > Pending work: http://drupal.org/project/issues/documentation/
> > List archives: http://lists.drupal.org/pipermail/documentation/
> >
> --
> Pending work: http://drupal.org/project/issues/documentation/
> List archives: http://lists.drupal.org/pipermail/documentation/
> 
>