3 ms·
Even better than gists is to use actual running code for examples. http://gist-it.appspot.com/ http://gist-it.appspot.com/ allows you to do that, which we util
by bryanlarsen 14y ago
Even better than gists is to use actual running code for examples.
http://gist-it.appspot.com/ http://gist-it.appspot.com/ allows you to do that, which we utilize in this tutorial: http://cookbook.hobocentral.net/tutorials/caching http://cookbook.hobocentral.net/tutorials/caching
Even more radical is using git for a step-by-step tutorial: http://cookbook.hobocentral.net/tutorials/agility http://cookbook.hobocentral.net/tutorials/agility is completely assembled from the commits of this repository: https://github.com/Hobo/agility-gitorial/commits/master https://github.com/Hobo/agility-gitorial/commits/master
- truebosko 14y agoThat's similar to http://bl.ocks.org/ http://bl.ocks.org/
- benzittlau 14y agoThese are cool examples, but I'm not convinced of the utility here. Using a git history as a tutorial feels like trying to shim a wrench into a hammer. What is needed is a form of CMS which can link some content to a patch, and I feel like there are better options out there for accomplishing that. It seems like maintaining this documentation going forward would be very challenging as git is not designed around making editing the past easy.