This is in response to a minor complaint about the text size on
mastodon, which I agree with:
https://chaos.social/@imadnyc@mstdn.social/112961604691513932
I personally agree that 20px does not feel right, and more to the point,
our previous type scale was really odd: body text was 1.25rem (20px),
while the nav links were 1rem (16px). It seems like the intent of this
was to make it so that the body text was not 16px, which felt too small
(and does to me too).
However, it seems to me like the *actual* solution here is to set the
entire type scale overall larger, then decrease the size of any type
that looks particularly silly.
Thus, I've set the root font-size to 18px (via a percentage of 112.5%)
instead of the default 16px, which will fix all the 1rem font sizes
elsewhere in the site, to *make* 1rem a reasonable body text size.
I found it really hard to read what was actually code, so this change
adds a very subtle hint of colour around all the code which has cheeky
border radii. I've also cheekily made the font a tiny bit smaller for
inline code so that even with the required padding, it does not mess up
the line spacing visibly.
I *believe* this will just mean HTML inside summaries is rendered rather
than being stripped, but when it strips HTML it doesn't render HTML
entities like `“`, which is what this commit is fixing.
Chrome and Safari default <svg> width and height to 'auto', which
expands the viewport to fit the pixels within. Safari doesn't, and
the viewport collapses to 0x0 unless explicitly expanded.
Firefox calculates the viewport's natural dimensions to be 16x18,
so I used those values.
Fixes#8
The width does nothing as far as I can tell, and the height makes
the clickable boxes much higher than they need to, overlapping with
the paragraph before the button in the footer.
