Blog: add post with all bech32 content to date

[harding]

Closes #128

This moves each bech32 sending support section into a separate includable file and then includes each of them in two different places: first, in the newsletter that originally included them; second, in a blog post backdated to the start of our series. I think this makes the combined content highly accessible, as it's all easily searchable using find-in-page.

This required moving links around and also moving where we included references.md in some previous newsletters (because it contains variable definitions, it must appear before we use those variables, which means including it before the subsequently-included bech32 sections. However, it can't go at the very top of the file, since that breaks the automatic first-paragraph summary used on the newsletter index page.)

A separate commit in this PR also adds a script that automates most of the work of creating the link reference definitions for old newsletters. Manually creating those links was annoying for me, even if it only took 30 seconds a week.

When making a change like this that makes a lot of backend changes but minimal frontend changes, my preferred testing method is comparing diffs of the rendered site. E.g.:

git checkout 4c551cc0    ## before these changes
make
cp -a _site _old_site
git checkout <this PR>
make
diff -ruN _old_site _site | colordiff | less -R

I think that looks good. (You can drop the -N from diff to suppress new files so that you only see the changes to existing files, which is a minimal diff.)

[moneyball]

tACK. Note that I only built locally and tested - I didn't review the actual changes, so someone else should do that.

I'm glad we're doing this now so that we have something easily shareable. It is already an impressive compilation.

I assume we plan to append each week's section to this when we publish the weekly newsletter?

Also this seems to belong in our scaling book too ... maybe repurpose it there in August when all 24 are complete?

[harding]

I assume we plan to append each week's section to this when we publish the weekly newsletter?

Yep. Sections from this point forward will be written in the _includes dir and then added to both that week's newsletter and this blog post.

[jnewbery]

Tested ACK 661e000.

Looks great. Thanks Dave!

[jnewbery]

If you s/scheduled to run/running for/ we won't need to update this once the series is complete.

[jnewbery]

As above, consider s/scheduled to run/running for/.

[jnewbery]

snooze-lose 👍

[harding]

@jnewbery the sentence has been rephrased. Thanks!

[jnewbery]

ACK 983a2fb. Thanks Dave!