This is not a new idea but I am happy to see new enthusiasm about it. I created this wiki some time ago:
https://mdp.cti.depaul.edu/web2py_wiki/default/wiki/main versioning was missing. Do you think we need another one or additional features? You can also create new pages in AlterEgo. Massimo On Feb 24, 8:08 am, Alexandre Miguel de Andrade Souza <alexandrema...@gmail.com> wrote: > I think I could help in documentation. > > Massimo, can you create a wiki to we begin to work? > > 2009/2/24 Timothy Farrell <tfarr...@swgen.com> > > > > > > > This is why I pushed for having a wiki. Granted that now the wiki's CSS > > needs to be fixed, but this allows us all to have community-based > > documentation. With no offense intended, I don't think Massimo should > > be the one to write the docs. He's done a lot and things are plain to > > him that are not plain to others (and he seems to have a broken keyboard). > > > My charge is that feature implementers should document their features > > well and we should have a few people dedicated to making the > > documentation clean and friendly. This can all be done on the wiki, or > > we could do it in a prettier fashion with Sphinx. > > > The Linux kernel has a group of programmers called the kernel janitors. > > We need some documentation janitors. Volunteers? > > > Joe Barnhart wrote: > > > It seems to me that we have reached a critical point in web2py. > > > > The development of web2py has been at such an accelerated pace that > > > the environment has far outpaced its pool of documentation and > > > examples. I am using the latest stable version and loving the new > > > capabilities of "auth" and "crud", but I find I'm spending an > > > increasing amount of time in the gluon directory, trying to read and > > > understand the source. > > > > Maissmo's web2py book is an excellent starting point, and it got me > > > through the basics and well into my first web2py site. But there is > > > so much to learn -- so many ways of solving the common problems that > > > surface again and again. I look to the wiki and the mailing list, but > > > the answers just aren't there, or are so diffuse that it's hard to > > > find them. > > > > This is a critical point because we have the chance to make web2py > > > "mainstream", but only if we can get the information flowing at a pace > > > equivalent to development. Documenting is not as fun as development. > > > But if users must read the source to understand how to create sites, > > > we will never turn the corner and make web2py the success it could be. > > > > From where I sit, documentation and examples are the #1 problem faced > > > by web2py today. > > > -- > > Timothy Farrell <tfarr...@swgen.com> > > Computer Guy > > Statewide General Insurance Agency (www.swgen.com) > > -- > Atenciosamente > > -- > ========================= > Alexandre Miguel de Andrade Souza > Hipercenter.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
