Deploy a new version of the site

[Changaco]

http://aspen.io/ really needs to be updated to reflect the big changes of the past few weeks.

Todo

• are these really our backgrounds?
• 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
• 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
  • star buttons in framework listing
  • dispatch visual
  • body copy on FAQ
  • maybe use rems for text?
  • GitHub ribbon
• syntax-highlight the simplates example (with what highlighter? 😞 )
• build out simplate support cards
• where do plugins fit?
• favicon
• acknowledge sources (fonts, backgrounds, etc.(?))
• fix FOUC for star button
• test with multiple browsers

[Changaco]

First: do we want to import parts of the current content into this repo, or start from scratch?

[chadwhitacre]

@Changaco I say we start from scratch. I think aspen.io can now be a single static page, and all of the documentation that has been there can now be in Read the Docs for each subproject (aspen.py, Pando, Flask-Aspen, django-aspen, etc.).

[Changaco]

@whit537 Can you take this one? It'd be nice to deploy it at the same time we release the new aspen (and the first pando along if possible).

[chadwhitacre]

Sure thing. Do you have a timeframe in mind? We had talked about September as a target for Aspen 1.0, though that was pre-Pando.

[Changaco]

Well, Aspen is pretty much ready, it even was before the last PR we just merged, and Pando should be similarly ready once AspenWeb/pando.py#556 is merged, so really we could release soon. How about a 0.90 release for Aspen in the next few weeks, and 1.0 in September?

[chadwhitacre]

Note to self: don't forget to change security.txt (AspenWeb/salon#3 (comment)).

[chadwhitacre]

I'm taking this as my top-level ticket for what I need to get done before 1.0 (AspenWeb/pando.py#357). I expect it to fan out into other work but fundamentally what we want to do on September 19 is be able to say "Hey check out http://aspen.io/ for the new Aspen 1.0 and friends!"

[chadwhitacre]

I think we need to come up with some realistic expectations about how much we're actually going to market and promote Aspen/Pando. I think the answer is "not very much." I'm not an /r/python regular and I'm not looking to be, to be honest. I'll talk about it some on Twitter, but I don't really want to pay attention to the aspen_io Twitter account.

[chadwhitacre]

Bringing this over from AspenWeb/aspen.py#1 (comment):

[chadwhitacre]

... and this one from AspenWeb/salon#1 (comment):

[chadwhitacre]

At this point I am leaning towards something like the latter, a visualization of the repos in our org, basically.