Colophon

~kqr

 

I try to keep a consistent visual style across all my productions. These are some general observations.

Keep in mind there is no ready-made recipe for a good visual style. It's all blood, sweat, and tears. (Doubly so if you need to support Microsoft products.)

Typography

Body text is set in Whitman by Kent Lew, starting at 12 over 17 points and increasing with increased display resolution. Paragraphs are indented by an em on the first line. Main title is also set in Whitman, 2–3 em.

First-level headings are set in Cooper Hewitt Bold, by Chester Jenkins, 1–1.5 em, with about 2 ems of space above, and 1 em of space below. Second-level headings also use Cooper Hewitt Bold, but at 1 em. About 1.8 ems of space above, but only half an em below. Cooper Hewitt is also used in medium shapes for navigation, and italic for captions. These are generally set slightly smaller than the body text.

Fixed-width text is set in Hack by Source Foundry, again slightly smaller than the body text. I still probably like Luxi Mono more, but Hack is many times less likely to upset anyone.

Text is solid black onto a background of either solid white or, if the medium permits, a slightly warm off-white (#fffcf9). Hyperlinks are a humanistic orangey-brown (#9e7140) in order to be visible but not distracting.

The length of the lines vary a bit depending on the type of the document. For information-dense productions, lines can be 70–80 characters. When the subject matter is lighter, I keep lines below 65 characters.

Editing

I have a strong preference for drafting and editing documents in Org.

If there's a reasonable way to get from Org to the end product, I don't edit the raw end product directly (be it html, pdf or whatnot.) Sometimes I write html manually. Sometimes I use Scribus. I virtually never write LaTeX, plain text, or Markdown anymore – Org can always give me that.

Privacy

I no longer run a self-hosted Matomo instance. To gauge interest in topics I have written about, I run a Perl script that summarises the nginx log instead.

Hosting

I host my things on virtual servers with old school Unix-style technologies: ssh, Freebsd, Debian, nginx, rsync, Postgresql, cfengine, that type of thing. You can do a lot with the tried and true tools, as long as you know what you are doing. Not everything benefits from being Dockered into Nosql through Nodejs.

Math on the web runs through KaTeX, which is generally the only thing on my web pages that degrades for users with JavaScript turned off.