<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";
mso-fareast-language:EN-CA;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-CA link=blue vlink=purple><div class=WordSection1><p class=MsoNormal>I’m following this thread and trying to visualize how the connector pages might work.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I’ve been using a menu like the image below from my AW days and reluctant to let it go. ‘Parts’ (chapters?) are listed on the left, and when clicked on, ‘Modules’ (basically groupings of pages) appear in a sub menu on the right. I’m reading your posts Stephanie and wondering if you are doing something similar to this?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><img width=292 height=225 id="Picture_x0020_1" src="cid:image002.jpg@01CD100F.56F1BF50"><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Since this is the desktop version I can build separate frameworks for each part and jump there. In toolkits however, with a linear flow, I can’t do that. Is there a way with the connector pages to duplicate the type of navigation above – parts/modules – where module 2 jumps to let’s say page 5 – 10 then returns to the main menu, module 3 jumps to page 11-15 then back to the main menu, etc? So…we have a great big linear toolkits presentation but the menu breaks it into parts/modules ‘learning chunks’. Is that possible?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Also - once the user ‘returns’ to the main menu, is there a way to mark (color change, checkmark etc.) which menu choice has been completed? <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thanks<o:p></o:p></p><p class=MsoNormal>RonM2<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><p class=MsoNormal>Further to my earlier email regarding the Menu Connector page. I have now added the facility to supply the page with a list of pageIDs that you want listed in the menu. That way you could have a project set up as follows<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Title page<o:p></o:p></p></div><div><p class=MsoNormal>Main menu - listing pages Introduction, Chapter 1 menu, Chapter 2 menu, Chapter 3 menu etc.<o:p></o:p></p></div><div><p class=MsoNormal>Introduction<o:p></o:p></p></div><div><p class=MsoNormal>Chapter 1 menu - listing all the pages in chapter 1<o:p></o:p></p></div><div><p class=MsoNormal>Pages 1 - n of chapter 1<o:p></o:p></p></div><div><p class=MsoNormal>Chapter 2 menu - listing all the pages in chapter 2<o:p></o:p></p></div><div><p class=MsoNormal>Pages 1 - n of chapter 2<o:p></o:p></p></div><div><p class=MsoNormal>Chapter 3 menu<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>etc.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>That should cover pretty much any project structure.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Kind regards<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Johnathan <o:p></o:p></p></div></div></body></html>