On 3/24/08, Ben Bangert <[EMAIL PROTECTED]> wrote: > > I've been reading carefully through the docs for Sphinx ( > http://sphinx.pocoo.org/ > ) the past few days, and am quite sold on it at this point. As such, > I'd like to assemble a group of other people who are interested in > working on the docs for Pylons.
Good news. I always thought Pylons docs seemed poor, esp. compared to Django. > The parts in that list we'll be including in our docs is (and the > approximate section in the Pylons docs): > Pylons (Advanced Pylons) > SQLAlchemy (Models - Working with Databases) > Mako (Templating) > Beaker (Sessions & Caching) > WebHelpers (Templating - Helpers) > WebOb (Working with the Request/Response) > FormEncode (Models - Validating user input) > WebTest (Testing - web application testing) > Nose (Testing - running the tests, writing them, etc) > Paster (Advanced Pylons - WSGI, CLI scripts, etc) > WebError (Testing/Debugging - troubleshooting) > Babel (Internationalization) > > If you'd like to help work on the docs in any of these ways: > - Write docs > - Grammar / spelling checking > - Copy editing (consistent usage of terms, tone of voice, etc.) > - Technical review I'd like to help with #1 (write docs) and may be #4. I'm not a native English speaker so I'll refrain from #2,#3. As for package coverage, I'm interested in documenting Nose, Babel, WebOb. Though these packages have a better docs than the core Pylons (of course, they are much simpler conceptually as well). Max. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-devel" group. To post to this group, send email to pylons-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en -~----------~----~----~----~------~----~------~--~---
