remove underlines for TOC, blog/post title, page links
less goofy, more standard CSS link underlines (thx again to Said Achmiz)
superscript line spacing fix
check in
I have been informed that CSS doesn't support //-comments
enable ToC on memoir pt. 3–4
memoir: pt. 3 section headers If both Said (private correspondence) and Ray (https://www.greaterwrong.com/posts/ZjXtjRQaD2b4PAser/a-hill-of-validity-in-defense-of-meaning/comment/Lmhum2tXLXzmbKvm5) agree that I need section headers, then I probably need section headers. I was feeling reluctant about it, but after doing it, I agree that this is a lot better. I have mixed feelings about giving the "Why are you a boy?" anecdote the prominence of its own section. (I wanted it to be subtle foreshadowing, but if it gets its own section, then it's blantant foreshadowing, which I choose to lampshade with a Suspiciously Specific Denial.) I'm not sure where the defaults were inherited from, but <h2> was too big and <h3> was too small, so I edit the CSS to make <h3> bigger. (Ideally, the titles would be anchor links ... do I need to write a Pelican patch or plugin for that?)
Nevada annotations I didn't think I was going to get around to writing a Nevada review, but I realized I did want to mention it in my memoir (as one of the earlier clues in my 2016 Blanchpilling), and just dumping my annotations is easier than writing a proper review of a book in which nothing happens. The double-underline CSS is not working, but maybe I'll try poking at it again later.
comment counter links!
Markdown footnote styling! To think that I checked in that special footnotes plugin (2980fe3c "not thinking in nested parentheticals vs. installing a footnote plugin", 19 Feb 2018), when it turns out that footnote capability was part of Markdown itself all along!
drafting "Reply to the Unit" (featuring dialogue formatting) (Arguably the dialogue formatting should have been a separate commit in order to get a clean `git wordcount` (https://github.com/zackmdavis/dotfiles/blob/9fb0964a/bin/git-wordcount) of the actual writing progress here, but the perfect has reluctantly made some strategic concessions to its ally the good in the service of their common cause against the bad.)
photo credit CSS
check in
label axes (albeit uninformatively), explain diagram in a boxed aside
not thinking in nested parentheticals vs. installing a footnote plugin If I don't know how to make my thinking more linear and less tree-like, I might as well shove some of the subtrees into footnotes for legibility. I continue to by disappointed by the abysmal quality of the Pelican plugin/theme ecosystem, and very happy that I chose Pelican. (What I don't like, I can fix! Because Python! Rah!)
Creative Commons Attribution license
ditch overridden CSS rules It can't hurt, right??
tag cloud Markup adapted from the tag-cloud plugin README. It may be worth upstreaming my alphabetical-sort fix?
knock font size down 2 points On my screen, the blog has always looked better at 90%.
affirm background of metadata box The gray from the blockquote was spilling over into the metadata box. ... maybe there's a reason people like friendly, well-supported premade WordPress themes, rather than hacking their own statically-generated site?