That's great. I like the idea of having two or three layers of documentation, which would allow "Here is a basic overview of this feature, but click here to read all the details." I agree that people shouldn't have to Google to learn about older features, but only to learn about new features that haven't been formally documented in the book or in web2pyslices.
Michael On Feb 21, 5:05 pm, Anthony <[email protected]> wrote: > Bruno and Martin are working on a complete revamp ofwww.web2pyslices.com, > and they've got a lot of good > ideas:https://groups.google.com/d/topic/web2py/HkkZ_-kMUYE/discussion. If > you've > got ideas, let them know. I don't think we'll want a wiki in addition to the > new slices site -- the new site should accommodate everything. > > On Monday, February 21, 2011 5:53:04 PM UTC-5, pbreit wrote: > > I think it's gotta be a wiki. Slices is too structured. Here are models: > >http://code.djangoproject.com/wiki > > The Django wiki does not appear to be about users contributing > documentation. > > >http://wiki.rubyonrails.org/ > > Can't access the rails wiki right now.
