The RSS feeds use escaped HTML instead of XHTML, which improves
compatibility with certain feed readers (e.g. Microsoft Outlook).
Mention that Outlook uses its own weird engine for feed contents in my
web best practices article.
- Drop copyright symbol: I put it there because certain programs
explicitly look for it, but between rel=license, schema.org microdata,
and creative commons RDFa, I think scrapers should be covered.
- Update the theme-color and friends to work with my site's updated dark
theme.
Explicitly mark RSS feeds as "legacy" because I have joined the A-Town
Atom gang and they have a strict full-time attendance policy.
Thanks Forever for pointing out the spelling/grammar error here.
It's useless and invalid in those contexts, and removing it
significantly trims the file sizes.
Edit a post featuring a microdata code snippet to avoid conflicts.
The site now has polygot markup and can handle both XHTML5 and HTML5
parsing rules. My staging site will be XHTML but my main site will be
HTML5, just in case of parse errors.
If other tools (e.g. LightHouse) end up supporting XHTML5, I'll consider
switching the content-type to XHTML.
Add an RSS feed for notes. Next up, replacing the RSS navlink with a
page containing links to both my posts and notes RSS feeds. When I get
ATOM and WebSub, it'll have links ot those too.
Also fixed some typos and switched "Posted" to "Noted" in the context of
notes.
- Stop using draft WAI-ARIA 1.3 that isn't supported yet
- Make in-page links focusable across shortcodes/partials
- Replace existing in-page heading anchor links with a more accessible
option.
- Make backlinks aria-labelledby instead of giving them an aria-label,
so they can be translated.
They're not interactive elements and there's no hint that they should be
hovered on. Wrapping them in an <abbr> would just make the markup even
more overcomplicated, so I just dropped the titles.
Split up some verbose and repetitive templates to use nested templates.
Cache some templates that don't need to be re-built every time.
Reading time: switch "a" to "an" when followed by the number "8".
Improve whitespace alignment a bit.
- Don't auto-minify HTML but minify other resources, inc. the RSS feed
- Manually optimize whitespace a little to balance readability and
compressed size
- Goldmark 1.4.12 switches footnotes from a <section> to a <div>; update
regexes and stylesheet to account for this.
- Goldmark 1.4.12 allows multiple footnotes with the same reference; use
that.
- Clean up templates for unminified output. Also delete an unused class.
- Switch to unminified output by default.
Create a for <figcaption> and a render hook for code snippets inside
figures, replacing some ugly and complex inline HTML in my markdown
sources.
The only visible change is slightly worse HTML alignment and programming
language indicators (with microdata).
This removed the need to use one of the regex replacements in the
processed_content.html shortcode, and increased the minimum required
Hugo version to 0.93.
Some old browser engines don't fully support hyphenation, so they need
some extra help. Now, the entire site should fit in a 150 CSS-pixel wide
viewport.
Clean up some link text too so the text alone is more useful.
- Shrink some excessive alt text
- Remove some redundant links
- Screenreaders that split elements up aren't just on touchscreens
- Mention ChromeVox in list of screen readers
- Move TOC higher in page
- Spelling
- Drop more unused classes
Pulls content exported from Buku, so I don't have to commit every time I
add a bookmark.
Since I added another nav item, I had to adjust the navbar css.
- Move the end of the h-entry div up above the footer.
- Move syndicated link to Gemini capsule up into the byline so it gets
included in the now-smaller h-entry.
See https://github.com/nekr0z/static-webmentions/issues/1
- Wrap the <a> in a <span> to make the h-entry expose an author URL
(link to homepage). Useful for sending Webmentions.
- Switch from schema.org/Article to schema.org/BlogPosting
- Footer should contain date last built so people don't start scratching
their heads wondering why webmentions aren't showing up
- Add rel="nofollow ugc" to webmention links.
Statically grab and include webmentions during Hugo builds, no JS
involved. Hugo supports making web requests and parsing the resulting
JSON, so there was no need to use an external program either.
The sight of an animal using a JavaScript captivates Computer Scientists
and laymen alike, perhaps because it forces us to question some of our
ideas about human uniqueness.
Does the animal know how JavaScript works? Did it anticipate the need
for the tool and select it instead of Haskell or Zig?
To some, this fascination with JavaScript seems arbitrary and
anthropocentric; after all, animals engage in many other complex
activities, like Agile Planning and ordering Juice on the Internet.
However, we know that complex behaviour need not be cognitively
demanding.
JavaScript development can therefore provide a powerful window into the
minds of animals, and help us to learn what capacities we share with
them — and what might have changed to allow for the incontrovertibly
unique levels of technology shown by modern humans, such as integers and
block scope.
