- Stop using symlinks for template files, since those seem to have
broken.
- Force int data type for scratchpad integers since type inference seems
to have changed.
- Add generator info to Atom feed.
- Add generator version and commit hash to meta page, along with a link
to the last CI job if available.
- Use $JOB_URL to detect CI since that variable can be re-used to fetch
the URL to the latest CI logs.
- Support an indieweb person without a hyperlink.
- Don't put a period after "Changelog" links. Causes a line-break on
many popular phone screen sizes.
- Increase list padding so that ordered-list decimal markers have space
to fit without overflowing.
- Improve style for removing underline between h-card name and photo, so
it doesn't apply to any unnecessary elements.
- Reduce budget for document size.
- Adjust transcript shortcodes to also support <audio> elements.
- Add audio element shortcode based on <picture> shortcode
- Make <audio> elements match container width.
- Add a11y metadata to transcribed images to communicate the presence of
a transcript
- Fix relative urls in navigation: make them absolute urls, so that the
parsed navigation elements have the correct destinations.
This also switches image transcripts from a section with a heading to a
div with an ARIA label. That should reduce duplication between the
<summary> content and the heading while still being semantically sound.
I increased a bunch of tap targets to fit the recommended 48x48 sizes
and 56x56 non-overlapping regions, but unfortunately this caused
outlines to overlap with each other. This commit turns these elements
into inline-block elements and makes the necessary fixes to accomodate
this change.
- Re-order rel for my homepage's representative h-crad
- Fix the aria-current for the homepage
- Microdata: remove unnecessary "sameAs"
- Reduce "update without adding date updated" timeout to 15min
- Add u-uid and rel=me to my h-card on every page.
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.
