created legacy link redirects to new gitbooks content

Frijol commented 8 years ago

fixes https://github.com/tessel/tessel.io/issues/96 (cc @reconbot @HipsterBrown)

Merge order

Bit of a conundrum surrounding merge order between this PR and https://github.com/tessel/t2-docs/pull/51.

If https://github.com/tessel/t2-docs/pull/51 is merged first, our current tessel.io/docs goes down, because it's looking for specific URLs on Github which will be changed.

If this PR gets merged first, tessel.io/docs also goes down, because it's looking for specific pages on Gitbooks which don't exist first.

This is probably fine, since I don't think our traffic is so high that we can't have the docs page down for 15 minutes. So, the takeaway: both need to be merged at the same time.

Checking the work

Related to the above, I'm pretty sure I got all the right old links mapped to all the right new links, but cannot test because https://github.com/tessel/t2-docs/pull/51 isn't merged/live yet. So we should check all the links right away once both PR's are merged/deployed. (And please review them carefully beforehand to ensure they are theoretically correct.)

Couple of other things

I'll make line notes. There are a few specific oddities.

reconbot commented 8 years ago

+1 on the merge order

reconbot commented 8 years ago

I'm going for it, I think it would be a very nice thing to have in place for nodebots day.

tessel / tessel.io