Forgot to update this link when I renamed the video files.

* Homebrew install tested and working
* Checkout tested and working

Ready for prime time.

Now that it takes two commands to install the program, make it easier
for visitors to copy-paste the commands into their shell by preventing
selection of the '$' prompt character.

This allows us to keep the prompt to indicate that these are shell
commands and still make copy-pasting easier.

As a side note, decided not to add the `brew services` command to the
instructions on the thank-you page because if DomeKey is already
running when you license it, you need to restart it for the license to
take effect.

Since the program doesn't work unless the daemon is launched, it makes
sense that this should be an installation step in order to actually use
the program.

Apparently, Safari doesn't support h.264-encoded video with a frame size
larger than 640x480. Learned about it from this Stack Overflow answer:
https://stackoverflow.com/questions/20347352/html5-video-tag-not-working-in-safari-iphone-and-ipad/31247386#31247386

According to Apple's documentation:

> The following compression standards are supported:
>
> * H.264 Baseline Profile Level 3.0 video, up to 640 x 480 at 30 fps.
>   Note that B frames are not supported in the Baseline profile.
> * MPEG-4 Part 2 video (Simple Profile)
> * AAC-LC audio, up to 48 kHz

(https://developer.apple.com/library/archive/documentation/AppleApplications/Reference/SafariWebContent/CreatingVideoforSafarioniPhone/CreatingVideoforSafarioniPhone.html#//apple_ref/doc/uid/TP40006514-SW9)

Seems a bit odd to me, but I don't know video, so sure, why not?

Since I want to keep my atypical video dimensions, encode it in MPEG-4
following this guide:
https://trac.ffmpeg.org/wiki/Encode/MPEG-4

Unfortunately, this gives us a 12 Mb video file (compared to the h.264's
~3 Mb). Reducing the quality just didn't produce a decent-looking
output.

Deciding to keep the h.264 version, just in case it's supported
somewhere, because it's the version with the smallest file size.

Otherwise it gets rendered small when the page first loads, then expands
to the correct dimensions after the page has loaded. This removes the
jump-cut effect.

The scroll position is now kept when the modal overlay opens.

Not committing the video files. They're only 3 & 4 megabytes each, but
that still seems a bit too much to keep in version control.

Add the video to the home page and center it in the content area. We
give it a negative margin to center it since it's wider than the
container.

Just tested the program on 10.8 and it didn't work. It ran just fine,
but didn't run map actions, and I'm not sure why. Used the release
build, so I didn't debug it at all.

Since I'm planning an imminent public release, just set the minimum to
an OS version that we know for sure works.

In the future, I'd still like to get the program working on 10.8. We can
always bring down the minimum OS version.