In addition to removing the now unused pager block.

The added blocks collect the HTML used within them, which will in turn
be inserted at the proper location.

This mostly serves my need for everything to be tidy, but it also serves
the need for everything to be *correct*.

This allows the developer to make CSS rules to improve the behaviour of
the site when JavaScript is not enabled.

The 0.001 wasn't thoroughly tested. It turns out that with chrome it
ends up activating on the 768 breakpoint even though it shouldn't have.

At 0.01 it also triggers.

This is now set back to a tenth of a pixel.

This made the gutter "carving" not happen, instead the maths as
made by LESS resulted in 47.8rem instead of 46rem.

The layout is tightly controlled in that orientation. Let the user
scroll instead.

This works around *parts* of a problem with way-too-narrow for comfort
sizes like the purported Galaxy Fold's 280 device pixel width for, what
I presume is, the external display.

Yes, we're scaling down the site, but we are **not** making it worse.
This is because the site structure will not be glitched out by the weird
proportions of those devices, and the users can still zoom-in.

In fact, the actual pixel density of their displays allows the user to
simply bring the phone closer to their face also!

Implement base JS + responsive menu