5 ms·
Sounds like a good idea. For the UI, I think you should allow double-click editing of specific paragraphs and sections, and the changes should be kept a list (g
by aonic 16y ago
Sounds like a good idea. For the UI, I think you should allow double-click editing of specific paragraphs and sections, and the changes should be kept a list (git status) that the user could request to be pulled by the maintainer.
P.S. is fb.com the new rumored FB email service? Any place to sign up for invites?
- matthodan 16y agoYup. You can sign up here: http://www.facebook.com/about/messages/ http://www.facebook.com/about/messages/
- matthodan 16y agoDo you think people would be interested in a full git workflow (i.e. you maintain the docs via a git branch that you push to the service)?
- aonic 16y agoI think that workflow might work if people (maintainers) are submitting HTML or README.md's or whatever for their docs. But for 'collaboration' with visitors/readers, it would need t be simple. I personally wouldn't want to pull out the command line and git clone, edit, commit, push just to get some tweaks or examples added to the docs unless it was a project I contributed to regularly. Another thing that might come in handy is something like code review tools that let you add comments for specific line numbers -- but for sections/paragraphs of the documentation. This could also serve as a revision history discussion as well as questions/comments on the information