[development] Book module break out features

Peter Wolanin pwolanin at gmail.com
Wed Mar 28 13:42:30 UTC 2007


Have you and Jeff looked at this SoC suggestion I wrote up:


I really don't like the proposal of allowing multiple parents for
nodes in this module- I think we lose more than we gain in terms of
complexity, performance, UI, etc when we move away from a single


---------- Forwarded message ----------
From: "Steven Peck" <speck at blkmtn.org>
To: <development at drupal.org>
Date: Tue, 27 Mar 2007 21:26:00 -0700
Subject: [development] Book module break out features

Jeff Eaton and I had chatted about book module off and on for the last
month when in Dries 'state of Drupal' presentation he mentioned some
of the same things as well.  At the code session I hunted several
people down and tried to come up with a task based list of steps to
get book module to the 'next' level for Drupal 6.

So here's the break down, if no one has any objections I will file
them as separate issue's.

Separate outline out of book/book content type and make a legacy
content type called book for migration purposes.

Allow for multiple root books with their own permissions and /menu blocks

Allow for next/prev automatic links on/off for a given book

    yes this can be done through the theme but a switch would make it
more accessible

Versioned pages for each book which affect the tree - support
branches/tags to allow for selecting which branch you want to see.

User input multiple relationship (on page or displayed separate block)

Menu system allows you to split menu's into multiple navigation
blocks.  Look at integrating book module to register it's menu's with
the menu module to create per book modules into the menu system. (per
Dries)  This would also bring it more in line with other core modules.

Allow for a given node to be tagged for more than one hierarchy

Use vamcode for the module (per Dries)

More information about the development mailing list