2009/3/4 Francisco Gama <francisco....@gmail.com> > > my turn: > > one wiki, and one wiki only. There are very organized and consistent > wikis. > > We define a set of templates for different kinds of pages to document > and then each page should have a status like: sketch, temporary, page, > permanent (blocked). > In last case we could even make a UI that enforced the correct usage > of existing templates. It's easy. > > 2 sources for documentation is a source of problems, nothing else.
*+1 * > > > On Feb 25, 1:38 am, Jason Brower <encomp...@gmail.com> wrote: > > As it looks like, it seems that a lot of the documentation and website > > are hosted on the university server. I have some dreamhost space if > > anyone wants to scrape up the 10 a year for domain name. They have a > > media wiki I can quickly setup there. Not sure if I can setup web2py, > > but I still think it would be useful to have a webpage that means > > something more to the project. Web2Py.org sounds obvious to me. :D > > Having a domain, to me, is a big step closer to a unified and more > > obvious place for documentation. > > Regards, > > Jason Brower > > > > On Tue, 2009-02-24 at 01:15 -0800, 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. > > > -- Atenciosamente -- ========================= Alexandre Andrade 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 -~----------~----~----~----~------~----~------~--~---
