On Jun 23, 2009, at 7:28 PM, Mike Orr wrote:

> Philip can also make changes on the website.

If others would like to help out with documentation (applying fixes  
for the comments on the website docs), I'd be happy to give some  
others the upload key. Docs can be regenerated using Sphinx, and  
uploaded to the website using the included upload script in the pylons  
source without anyone else needing to be present (its part of the  
PylonsHQ code-base to accept and replace the docs with uploaded ones).

For the website, if there's patches for that, I'd be happy to apply  
them as well.

> Well, yes it's there, but what do you do with it?  What are the
> standards for third -party docs such as Routes and WebHelpers that
> need to be both standalone, on their own website, and integrated with
> the Pylons docs?  What are the markup codes he's using for variable
> names and such?

I've gotten the Beaker site up to date. I can do the same with the  
Routes one as well, just need to fix-up the styling and such. If  
someone else has more time to throw at this, what needs to be done:
1) Copy over template files from beaker's docs dir so that the Routes  
docs get setup and styled
2) Update the index template to be appropriate for Routes
3) Let me know via a pull request, and I'll apply and upload to  
routes.groovie.org

I believe that's about it, oh, and maybe the Sphinx module docs need  
to be updated. Once Sphinx can generate it, I can go ahead and replace  
the routes.groovie.org site with it.

Anyone up for these tasks, or interested in updating the pylons/docs  
based on the comments, or fixing any website bugs?

Cheers,
Ben

--~--~---------~--~----~------------~-------~--~----~
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 
pylons-devel+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/pylons-devel?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to