<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 08.00.0681.000">
<TITLE>Book module break out features</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->
<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">Jeff Eaton and I had chatted about book module off and on for the last month when in Dries</FONT></SPAN><SPAN LANG="en-us"> <FONT FACE="Calibri">‘</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri">state of Drupal</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri">’</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri"></FONT></SPAN><SPAN LANG="en-us"> <FONT FACE="Calibri">presentation</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri"> he mentioned some of the same thin</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri">g</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri">s as well</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri">. 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</FONT></SPAN><SPAN LANG="en-us"> <FONT FACE="Calibri">‘</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri">next</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri">’</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri"> level</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri"> for Drupal 6</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri">.</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-us"></SPAN></P>
<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">So here</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri">’</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri">s the break down, if no one has any</FONT></SPAN><SPAN LANG="en-us"> <FONT FACE="Calibri">objections I will file them as</FONT></SPAN><SPAN LANG="en-us"> <FONT FACE="Calibri">separate</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri"> issue</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri">’</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri">s.</FONT></SPAN><SPAN LANG="en-us"></SPAN></P>
<P DIR=LTR><SPAN LANG="en-us"></SPAN></P>
<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">S</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri">eparate</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri"> outline out of book</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri">/book content type and make a</FONT></SPAN><SPAN LANG="en-us"> <FONT FACE="Calibri">legacy content type called book for migration purposes.</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri"></FONT></SPAN><SPAN LANG="en-us"> </SPAN></P>
<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">A</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri">llow for</FONT></SPAN><SPAN LANG="en-us"> <FONT FACE="Calibri">multiple</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri"> root books with their own permissions and /menu</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri"> blocks</FONT></SPAN><SPAN LANG="en-us"></SPAN></P>
<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">A</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri">llow for next/prev automatic links on/off for a given book</FONT></SPAN><SPAN LANG="en-us"></SPAN></P>
<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri"> </FONT></SPAN><SPAN LANG="en-us"> <FONT FACE="Calibri">yes this can be done through the theme but a switch would make it more</FONT></SPAN><SPAN LANG="en-us"> <FONT FACE="Calibri">accessible</FONT></SPAN><SPAN LANG="en-us"></SPAN></P>
<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">Versioned pages for each book which affect the tree - support branches/tags to allow for selecting which branch you want to see.</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">U</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri">ser input multiple relationship (on page or displayed</FONT></SPAN><SPAN LANG="en-us"> <FONT FACE="Calibri">separate</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri"> block)</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">M</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri">enu 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.</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri"> (per Dries)</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri"> This would also bring it more in</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri"></FONT></SPAN><SPAN LANG="en-us"> <FONT FACE="Calibri">line with other core modules.</FONT></SPAN><SPAN LANG="en-us"></SPAN></P>
<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">A</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri">llow for a given node to be tagged for more</FONT></SPAN><SPAN LANG="en-us"> <FONT FACE="Calibri">than</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri"> one</FONT></SPAN><SPAN LANG="en-us"> <FONT FACE="Calibri">hierarchy</FONT></SPAN><SPAN LANG="en-us"></SPAN></P>
<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">U</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri">se</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri"> vamcode for the module</FONT></SPAN><SPAN LANG="en-us"> <FONT FACE="Calibri">(per Dries)</FONT></SPAN><SPAN LANG="en-us"></SPAN></P>
</BODY>
</HTML>