apparently the markedOptions need to be wrapped inside more objects.
changed my mind on Jade. I'm new to this, so my opinions are fragile...

It occurs to me that maybe there's not much point in using Jade only
for its markup? The scripting functions are basically just JavaScript,
and so would compete with Eco. If I were to use Jade, I should really
go all the way, and use it for the whole templating process.

Markdown is a pretty limited, but does save some time for the basics,
and it's readability is unbeatable where it does work out. And where I
need more markup control, maybe it's okay to just write out the regular
HTML. Especially now that I've figured out what was wrong smartypants
in Marked, markdown seems sufficient for a markup shortcut.
changed written markup from Jade to Markdown.
template level metadata, so it's easier if collaborators change URL.

@coauthorsList() will be only for generating a single comma-separated
string for the <meta /> element.

This also means using eco even in story posts, if/when there are
collaborators.
styles for variant figures, and the comic script in image alt text.

Apparently CSS supports OpenType features like alternate figures and
stuff now? How long has *that* been a thing??

Funny, I don't think the font Alice supports a lot of those features
anyway. But it's good to know and get used to accommodating anyway, I
guess.
renamed YAML property to comic_script. "script" is ambiguous on the web.
removed unused `citations` YAML property.
added the first three stories from old WordPress site.

Should be enough for now to get started on designing the archive
sortings.
styles for archive-sort secondary menu. now to hide it on other pages...
Adjusted formatting to make it (slightly) more legible.