On Jan 20, 1:22 am, keymaster <[email protected]> wrote: > Firstly, Mark - a tremendous thank you and feelings of admiration for > your tremendous skills, good ideas, and all the time you and the rest > of the team are putting in, to make this great community what it is. > > > Leave a comment with your thoughts on the proposed documentation changes. > > Ability to download in other formats is important, agreed. > > Does Sphinx support the ability to do the following (as we have in the > current cookbook, but I don't see in the Python /Django docs): > > - ability for users to comment on the sections?
I hate to say this in public, but the comments on the book have not been successful in my eyes. They are filled with incorrect information, misleading information and content that should have been edits instead. > - ability for users to contribue docn? Yes all the docs will be on github. Contributing will be as simple as forking, editing and sending pull requests. There is also some thought being put towards creating a web editing interface behind sphinx generated docs as well. The web interface would probably work somewhat similarly to the existing book, with using git instead of a database for documentation content. > - ability to see recent changes? git log is great for that. Not only would you be able to see the logs for changes, but also the exact content changed as well. > > In general, I agree with a general philosophy of outsourcing (eg. > github, lighthouse, sphinx, etc.) all stuff which is not "core > business" as it just drains time. Me too, we're not experts in the realms we 'outsource' and using quality tools makes everyones life easier and simpler. -Mark -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cake-php
