Build out http://aspen.io/ for relaunch

[chadwhitacre]

Picks up from #1.

Todo

• build Aspen, Pando and Simplates logos as SVG
• clean up logo in footer
• build out "flavor" cards
• build "What is filesystem dispatch?" visualization
• reimplement "Impressions" client-side
• are these really our backgrounds?
• make /pando Build out http://aspen.io/ for relaunch #2 (comment)
• make /simplates Build out http://aspen.io/ for relaunch #2 (comment)
• are we templating these pages somehow? Build out http://aspen.io/ for relaunch #2 (comment)
• make it responsive
• syntax-highlight the simplates example (with what highlighter? 😞 )
• build out simplate support cards

[chadwhitacre]

Picking up from #1 (comment) ...

I'm thinking of having pages for http://aspen.io/pando and http://aspen.io/simplates, redirecting http://simplates.org/ to the latter.

Or maybe we can inline the simplates content into the main page, and just use Read the Docs for Pando. That way we don't have to deal with templating.

[chadwhitacre]

ML9 (AspenWeb/simplates.org#3) is now 404 (archive), so I'm not going to worry about bringing that over. We also don't need the pitch section since now it's framed as part of Aspen—the pitch is filesystem dispatch, simplates are a side-effect. Roughed in in a6a48d3.

[chadwhitacre]

BotBot indicates that #aspen on Freenode is moribund. I'm not going to worry about linking it.

[chadwhitacre]

P.S. I'm expecting to use GitHub pages to publish http://aspen.io/.

[chadwhitacre]

Actually, let's go back to #1. I'm going to commit directly to gh-pages since there's nothing really to merge into at this point. That way we can publish to http://new.aspen.io/ starting now! :-)