nhanb
Joined 14 years ago
Joined 14 years ago
I never thought of that as an option. Thanks for the tip haha.
However I never got around to finishing it, mainly because I couldn't decide on where to stop: should I also generate commits from all non-master branches etc.
I flirted with the idea of a browser-side repo viewer too, but re-implementing git packfile parsing in js didn't seem like something I'd want to spend my time on, so I moved on. Glad to see others pondering the same thing though.
Not the most original of ideas, but I was really sold on djot [1] and wanted something less fussy than pelican [2], so it just happened.
That's what the outer min() is for: it makes sure the font size caps out at 1.3em which usually translates to 16 x 1.3 = 20.8px, which is well within the recommended size range for prose anyway.
What that whole snippet does boils down to exactly what they said in the article:
> The main global stylesheet uses the browser default font size, smoothly scaled up to 130% on higher-resolution displays as the baseline for the body text of the whole document.
On a low-dpi screen, nothing changes. On a high-dpi one, if you haven't set your browser text size to something larger, this snippet saves you from tiny unreadable text. Also note that ctrl+ and ctrl- to zoom still work just fine. It's not as dramatic a change as the sibling comment said. You can try it out on their site to see for yourself.
> Websites in the, (late), 1990s were characterised by many things, but a typical list might include:
> - Serif fonts
Thanks for the tip on clamp() by the way, TIL.
font-size: min(max(1em, 1.3vw), 1.3em);
Which explains why it looks just right on my high-DPI Chromebook even though I haven't configured a big enough default font size for the browser.This is going to be the default font-size for all of my websites now (preceded by a fallback for maximum compatibility of course).