[pmwiki-users] Summary lines in cookbook recipe info

[the Other michael]

What PM said about pages for recipes, yes.

But... why does everybody seem to want to stick EVERYTHING into the cookbook?

If only there was some way to rapidly create web-content that was
organised into sub-groups.....

Christian has been very good with his EMacsModes group:
http://www.pmwiki.org/wiki/EmacsModes/EmacsModes

Does anybody else do this? Is it possible that the formality and
desire to keep things (Cookbook) clean (see below) intimidate others?

The Portland Pattern Repository -- http://c2.com/ppr/  -- neatly
allows for formal content, and a whole hodgepodge of _very_ useful
information. A hodgepodge that doesn't appear all that intimidating,
to be honest -- but in manner that does not detract from the
usefulness of its information.


-the Other michael
http://www.xradiograph.com/interference
http://www.xradiograph.com/wrottings


On 4/18/07, The Editor <editor at fast.st> wrote:

> Namely, that recipe writers only have one recipe page for each
> distinct recipe, and not a completely separate page for each possible
> application of it--like ZAPforum, ZAPblog, ZAPvote, etc..  Those could
> all be stored in a ZAP group and links to the sample uses of the
> recipe be made from the ZAP recipe page.
>
> I prefer a slightly fuller description (for those recipes with many
> features) on one page, than 8 or 10 separate pages each having their
> own description line. I suppose I could take that route if insisted,
> but in the interest of a cleaner cookbook, I'd rather not.
>
> Cheers,
> Dan