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.

[chadwhitacre]

The former hints at same.

[chadwhitacre]

https://www.instagram.com/p/7ZWW4mx8Bc/

[chadwhitacre]

https://www.etsy.com/listing/221076543/block-print-bigtooth-aspen-leaf-limited

[chadwhitacre]

http://newfs.s3.amazonaws.com/taxon-images-1000s1000/Salicaceae/populus-tremuloides-le-gmorrison.jpg

[chadwhitacre]

http://subtlepatterns.com/tree-bark/

[chadwhitacre]

http://photoephemeris.com/photographing-aspen

[chadwhitacre]

Repos:

        Flask-Aspen
        django-aspen
        pando.py
            aspen.py
                algorithm.py
                    dependency_injection.py
                filesystem_tree.py

        aspen.py-plugins

        aspen.go
        aspen.js
        aspen.rb

    aspen.io

        simplate.vim
        simplates.emacs

    simplates.org

salon

Should we rename aspen.{go,js,rb} to pando.*, or maybe simply get rid of them altogether?

Are aspen.py-plugins really still Aspen plugins? Is there more than one (Jinja2)?

[chadwhitacre]

There's a lot of work besides the Pando and Aspen 1.0 code itself to making this fly as an open source project:

• nice website
• documentation
• tutorials
• top users
• plugin ecosystem
• the Flask and Django shims
• simplate support for Vim and Emacs
• talking it up on /r/python, HN, Twitter, Changelog, Pycoders, StackOverflow, etc., etc.

[chadwhitacre]

https://github.com/theleagueof/orbitron

[chadwhitacre]

Harumph. Too similar to Flask. :-/

[chadwhitacre]

[chadwhitacre]

[chadwhitacre]

[chadwhitacre]

[chadwhitacre]

[chadwhitacre]

[chadwhitacre]

We'll need to kern these, but I like how they're lining up. Aspen, Pando, and Simplates all share the distinctive A and P from Blackout.

[chadwhitacre]

[Changaco]

Should we rename aspen.{go,js,rb} to pando.*, or maybe simply get rid of them altogether?

I suggest doing nothing other than changing the repo descriptions.

Are aspen.py-plugins really still Aspen plugins?

Yes, because simplates haven't been cut out of aspen yet.

Is there more than one (Jinja2)?

Yes, there's a tornado renderer that still works (at least in the tests).

[chadwhitacre]

[chadwhitacre]

[chadwhitacre]

http://plantsandrocks.blogspot.com/2012/10/final-trek.html

[chadwhitacre]

https://www.montetrumbull.com/galleries/05-close-to-nature/

[chadwhitacre]

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

[chadwhitacre]

Moving to #2 and closing here.

[chadwhitacre]

Reopening per #2 (comment).

[chadwhitacre]

I moved aspen.io and simplates.org from Gratipay's DNSimple account to my personal account. I had to sign up for the $5/mo plan to do so.

[chadwhitacre]

💃

[chadwhitacre]

New site is up on http://new.aspen.io/. Will keep iterating there ...

[chadwhitacre]

Now actually reopening. 😊

[chadwhitacre]

Django and Pando sure share a lotta letters. 😳

[chadwhitacre]

Cleaned up the frameworks listing.

[Changaco]

• syntax-highlight the simplates example (with what highlighter? 😞 )

I've had syntax highlighting of simplates in Kate for a while, and it supports exporting to HTML. Also, pandoc generates its highlighting code using Kate's syntax files, but you'd need to compile it yourself to add the simplates syntax.

[Changaco]

Here's the simplate example (modified to use Jinja2 for the HTML page) highlighted by Kate using 3 different themes:

<h2>Theme: Normal</h2>

<pre style='color:#1f1c1b;background-color:#ffffff;'>
<span style='color:#ff5500;'>import</span> random

<span style='color:#0057ae;background:#e0e9f8;'>[----]</span>
program <b>=</b> request.qs[<span style='color:#bf0303;'>'program'</span>]
excitement <b>=</b> <span style='color:#bf0303;'>&quot;!&quot;</span> <b>*</b> random.randint(<span style='color:#b08000;'>1</span>, <span style='color:#b08000;'>10</span>)

<span style='color:#0057ae;background:#e0e9f8;'>[----] text/html via jinja2</span>
<b>&lt;h1&gt;</b>Greetings, {{ program }}{{ excitement }}<b>&lt;/h1&gt;</b>

<span style='color:#0057ae;background:#e0e9f8;'>[----] text/plain via stdlib_format</span>
Greetings, {program}{excitement}

<span style='color:#0057ae;background:#e0e9f8;'>[----] application/json via json_dump</span>
{ &quot;program&quot;: program
, &quot;excitement&quot;: excitement
 }
</pre>

<h2>Theme: Breeze Dark</h2>

<pre style='color:#cfcfc2;background-color:#232629;'>
<span style='color:#27ae60;'>import</span> random

<span style='color:#2980b9;background:#153042;'>[----]</span>
program = request.qs[<span style='color:#f44f4f;'>'program'</span>]
excitement = <span style='color:#f44f4f;'>&quot;!&quot;</span> * random.randint(<span style='color:#f67400;'>1</span>, <span style='color:#f67400;'>10</span>)

<span style='color:#2980b9;background:#153042;'>[----] text/html via jinja2</span>
<b>&lt;h1&gt;</b>Greetings, {{ program }}{{ excitement }}<b>&lt;/h1&gt;</b>

<span style='color:#2980b9;background:#153042;'>[----] text/plain via stdlib_format</span>
Greetings, {program}{excitement}

<span style='color:#2980b9;background:#153042;'>[----] application/json via json_dump</span>
{ &quot;program&quot;: program
, &quot;excitement&quot;: excitement
 }
</pre>

<h2>Theme: Vim</h2>

<pre style='font-weight:bold;color:#b2b2b2;background-color:#000000;'>
<b><span style='color:#ff54ff;'>import</span></b><b> random</b>

<b><span style='color:#0095ff;background:#22226d;'>[----]</span></b>
<b>program </b><b>=</b><b> request.qs[</b><b><span style='color:#ff54ff;'>'program'</span></b><b>]</b>
<b>excitement </b><b>=</b><b> </b><b><span style='color:#ff54ff;'>&quot;!&quot;</span></b><b> </b><b>*</b><b> random.randint(</b><b><span style='color:#ff54ff;'>1</span></b><b>, </b><b><span style='color:#ff54ff;'>10</span></b><b>)</b>

<b><span style='color:#0095ff;background:#22226d;'>[----] text/html via jinja2</span></b>
<b><span style='color:#dede49;'>&lt;h1&gt;</span></b><b>Greetings, {{ program }}{{ excitement }}</b><b><span style='color:#dede49;'>&lt;/h1&gt;</span></b>

<b><span style='color:#0095ff;background:#22226d;'>[----] text/plain via stdlib_format</span></b>
Greetings, {program}{excitement}

<b><span style='color:#0095ff;background:#22226d;'>[----] application/json via json_dump</span></b>
{ &quot;program&quot;: program
, &quot;excitement&quot;: excitement
 }
</pre>

[chadwhitacre]

Here's the simplate example (modified to use Jinja2 for the HTML page) highlighted by Kate using 3 different themes:

!m @Changaco 💃

Updated in 6bc96c2.

[chadwhitacre]

The plugins should all get their own RtD subsite under aspen.io as well.

[chadwhitacre]

@Changaco You okay with what is apparently our new logo? You okay with how the new homepage is shaping up?

[chadwhitacre]

Here's the 512 PNG that I used for GitHub:

[Changaco]

You okay with what is apparently our new logo? You okay with how the new homepage is shaping up?

Yes and yes, although the completely blacked-out PANDO logo looks weird to me.

[chadwhitacre]

http://qrohlf.com/trianglify/