Have you seen the medium.com in-context notes? That would be a great way to bring it all together: https://medium.com/about/why-medium-notes-are-different-and-how-to-use-them-well-5972c72b18f2
There's even a jQuery clone that could be used: https://github.com/aroc/side-comments On Thursday, September 18, 2014 11:07:44 AM UTC+12, Derek wrote: > > I'd like to see a wiki... it could be run on web2py even... > > On Tuesday, September 16, 2014 3:12:52 PM UTC-7, Anthony wrote: >> >> Maybe submit a Github issue in the book repo requesting this feature. >> >> Anthony >> >> On Tuesday, September 16, 2014 6:12:06 PM UTC-4, Anthony wrote: >>> >>> Agreed, but for the most part, if something is truly lacking from the >>> documentation, it would be best if it could be included in the >>> documentation itself, rather than in a long list of unorganized comments at >>> the bottom of the page. You can always make a pull request on the book repo >>> (https://github.com/mdipierro/web2py-book) for direct changes to the >>> documentation. >>> >>> Allowing user comments/feedback isn't a bad idea, though, but we would >>> probably have to change the UI -- currently each chapter is a very long >>> HTML page, and putting comments at the bottom would in many cases place >>> them very far from the relevant context in the chapter. >>> >>> Note, the old version of the book did in fact allow comments at the >>> bottom of each page (though there was no upvote/downvote feature), but that >>> functionality was not migrated to the newer book app. >>> >>> Anthony >>> >>> On Tuesday, September 16, 2014 6:02:42 PM UTC-4, Robin Manoli wrote: >>>> >>>> It's not really what I'm looking for. There are many benefits to the >>>> php documentation way: >>>> 1. the comments are where you are looking for help >>>> 2. when you are looking for help, and find a solution of your own, you >>>> can post it where you were looking >>>> 3. the current documentation is unclear in many places, and it's not >>>> very efficient to browse around the form/slices/stackoverflow/examples to >>>> get to the solution, when it could already be there where you look first >>>> 4. the documentation could become verbose instead of lacking >>>> 5. there are many little tricks that i have read about in the forum >>>> that i couldn't find in the documentation... if all these tricks would be >>>> more accessible, web2py's many hidden features could be used more >>>> >>>> Den torsdagen den 11:e september 2014 kl. 00:27:10 UTC+2 skrev Anthony: >>>>> >>>>> It's not embedded with the main documentation, but for user >>>>> contributed content, we do have http://www.web2pyslices.com/home. >>>>> >>>>> Anthony >>>>> >>>>> On Wednesday, September 10, 2014 5:55:36 PM UTC-4, Robin Manoli wrote: >>>>>> >>>>>> Hey, >>>>>> the php documentation has user comments with examples of how to use >>>>>> different functions. This is a great complement to their documentation. >>>>>> >>>>>> With web2py I have stumbled upon many things in these forums that I >>>>>> have not seen in the documentation. I'm not sure how often you update >>>>>> it, >>>>>> since I keep finding new things there too. >>>>>> >>>>>> Still, don't you think it would be better if we all could contribute >>>>>> with common and examples to an api-type of documentation for web2py? I >>>>>> think the php documentation does this really well. >>>>>> >>>>> -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
