SEO suggestions

[NPrescott]

A couple of things off the top of my head regarding #14:

• Use the description and website field for the repository to create a logical "crawl" for robots, like I have here
• Think about following up on posts like this, "Following up 2 years later - there is now http://pretty-print.net for this very purpose" or similar.
• Instead of linking to the Github "rationale" create an about or rationale page on pretty-print.net itself with that information
• Add a bit of text or instruction to the main application page itself to increase any possible "content" scoring. Paste EDN data or Clojure code below to have it validated and properly formatted (I notice you don't mention validation but the formatter doesn't seem to work presently with invalid Clojure code)

The actual commits aren't styled at all and are instead just to give an idea of what I'm talking about.

[comamitc]

I'd like to see the /about.html route be embedded in the single page router and the markup to be converted to sablono.

The instruction content might not pass the @oakmac test of clean design.