[pmwiki-users] Proposal: Recipe Structure Change

[Tegan Dowling]

On 5/23/06, Joachim Durchholz <jo at durchholz.org> wrote:
>
>   ...comments ... often contains
> a wealth of valuable tips and alternate approaches that the original
> author didn't think about. Splitting it off into a separate page
> increases the probability that visitors will overlook it - it's just
> that additional click away.
> Scrolling down is so much easier (and you can easier refer back to the
> actual recipe).


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?

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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: /pipermail/pmwiki-users/attachments/20060523/b146df3e/attachment.html