The miniature-octo-ironman from timproctor

Overview

Install dependencies with	`rake bootstrap`
Run tests with	`rake cuke`
Run server with	`rake server` (once someone does Rake task for server anyway)

I can embed a Ruby snippet into a markdown page and see an editor
I can run the code in the editor and see the output (Follow along with progress at #12)

Pick an issue:
- Look for one that is not assigned
- Sub issues of #12 would be super helpful :)
- Also #17 is small.
Try to work in small steps that you can push up to master without breaking tests
Make sure any relevant behaviour is tested, so we don't break your shit when we change it (we'll do the same for you, so you can change our shit without fear)
In any relevant commits, mention the issue number (e.g. #17), they will automatically be associated with the issue (more on linking)
When your commits are adequate to complete your story, ask for a code review.

Change anything you want (try to understand why it is the way it is, ask others if you need context)
Try to work in small enough steps that you can push them multiple times per day (ideally, you can push after each commit, though you don't necessarily)
Everyone's local master should be hovering around origin/master so that all changes are small with low likelihood of conflict, and everyone has as much of everyone else's work as possible, so that no one is being held up by unmerged features.
Have reasonable tests on your features so we know if we break them. If you're having difficulty knowing what or how to do this, come ask.
Never push failing tests to master, you'll break everyone else's ability to work on their thing, they'll have to deal with your failure.
See a problem? Fix it. Have an idea? Open an issue.

manifest of lesson names to git repositories (ie gist) rather than having to edit the source of the server to change a lesson
maybe scoped by content owner
maybe overridable language for the editor