On 5/10/07, Christoph Haas <[EMAIL PROTECTED]> wrote:
>
> On Thu, May 10, 2007 at 12:47:21PM -0700, Shannon -jj Behrens wrote:
> > I finally got around to reading "Concepts of Pylons"
> > <http://docs.pythonweb.org/display/pylonscookbook/Concepts+of+Pylons>,
> > and I think it's a very well written introduction for newbies to the
> > Python Web world.  It makes sense to integrate this into the main
> > Pylons documentation: "If you're new to Web programming in Python,
> > read ..."
>
> In favor! :)
>
> Last time we talked about it the article was supposed to become a
> possible introduction chapter to the Pylons book. But recently I just
> heard voices that a handbook of some sort makes no sense and that
> docs.pythonweb.org is supposed to be just a collection of recipes and
> tutorials. I'm still willing to support a book concept though.

There are some sections of the docs.pythonweb.org that aren't public
yet.  One is the beginning of a handbook-style manual to replace the
official documentation on the pylonshq site.  The idea is that anybody
can contribute cookbook recipes and articles, and the best of those
will be merged into the official docs if they address a central topic.
 But if people wanted to write additional book-like items, I'm sure
there would be no objection to adding sections for them if they target
a significant distinct audience.  E.g., we don't need three large
tutorials.  I would start off with a Cookbook article or outline
first, and then if it threatens to grow into an unmanageably large
number of pages, petition for a new wiki section for it.

-- 
Mike Orr <[EMAIL PROTECTED]>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/pylons-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to