Rust blinky (experimental, don't merge)

[Frijol]

Couldn't resist seeing what this would look like :) cc @tcr

[Frijol]

Some interesting things to solve in world of a Rust start experience:

1. We don't actually have to change every page. The installation, wifi, etc. are pretty much the same. With this in mind, do we want to make fully divergent start experiences for JS vs Rust? I had been planning to treat it like a separate spoken language, a /rust in the URL, but this seems to have the potential to get in its own way.
2. In the context of De-emphasize modules #144 and https://github.com/tessel/t2-docs/blob/tcr-modules/Modules/Accelerometer.md (exploring moving module quickstarts from t2-start to t2-docs), we could have very little divergence between the JS and Rust experiences
3. We've also discussed moving some of the other exercises (ap etc.) to t2-docs under the Tutorials section. How far do we want to go with this?

Based on the thought process above, I'm starting to think t2-start should undergo some thoughtful design review. For instance: does it really need its own separate site, or should it just be part of the docs?

Somebody chime in on this, I feel like I'm approaching a cliff edge after which our beloved short time-to-awesome gets sacrificed. Or, maybe the time-to-awesome shrinks with a tighter t2-start/t2-docs connection?

@HipsterBrown @tcr @rwaldron @reconbot

[rwaldron]

I'm not really sure what the right course is (sorry, but I wanted to respond either way)

[tcr]

I have opinions but I will have to express them once I have time to address them. I support start as a separate site and experience, similar to Docker's separate start experience.