On 5/23/06, <b class="gmail_sendername">Joachim Durchholz</b> <<a href="mailto:jo@durchholz.org">jo@durchholz.org</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
...comments ... often contains<br>a wealth of valuable tips and alternate approaches that the original<br>author didn't think about. Splitting it off into a separate page<br>increases the probability that visitors will overlook it - it's just
<br>that additional click away.<br>Scrolling down is so much easier (and you can easier refer back to the<br>actual recipe).</blockquote><div><br>This is where the PageTableOfContents recipe would really be useful. I use it with all my installations and have never encountered an issue with it - could it be considered for the core and used by default on the cookbook pages?
<br><br>Keeping all content on one page does have real advantages to "shoppers" (like seeing that there are problems with a recipe that doesn't live up to its "marketing", and isn't ready for general use), as does having more structure in the template, which helps a recipe's maintainer(s) and user-participants organize their contributions to the page in a logical way. The drawback to one long page is...it's long, and often complicated. You lose track of where you are and what's ahead. A
t.o.c. (and some template-included "back to top" links along the way) would help readers find their way around.<br></div><br></div>