seirdy.one/layouts/index.html

{{ define "main" -}}
<main>
<h1 id="h1" tabindex="-1">Seirdy’s Home</h1>
<p itemprop="description">{{ .Site.Params.Description }}</p>
<hr />
<div class="narrow">
{{ partial "processed-content.html" . }}
{{ partial "posts.html" . }}
{{ partial "webrings.html" . }}
</div>
</main>
{{ end }}
-												Remove extra newlines

											
										
										
											2022-05-31 17:11:52 -07:00
+								{{ define "main" -}}
-												Make the skip-link point to h1 instead of main

Link targets need to be focusable to work with VoiceOver.

Making <main> focusable causes some side-effects, like making the TAB
key go to the beginning of <main> instead of the element after the
currently-clicked region.

Also removes the annoying outline around "main" in some non-mainstream
browsers, without having to add extra CSS.

											
										
										
											2022-07-13 08:31:20 -07:00
+								<main>
 								<h1 id="h1" tabindex="-1">Seirdy’s Home</h1>
-												Replace homepage <aside> with page description

IBM Equal Access A11y Checker caught an <aside> without a label. Figured
this was a good opportunity to instead use the site description.

While I was at it, I expanded said site description and used it
properly.

											
										
										
											2022-07-12 22:55:45 -07:00
+								<p itemprop="description">{{ .Site.Params.Description }}</p>
-												Minor markup adjustments

- Move a horizontal rule from inside an element to outside it
- Add a horizontal rule
- Remove redundant info from some webmention titles

											
										
										
											2022-08-02 18:20:52 -07:00
+								<hr />
-												Refactor to make more body text narrow

Now more text should fall within WCAG limits.

											
										
										
											2022-07-11 17:20:36 -07:00
+								<div class="narrow">
-												Switch to XHTML5 markup

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.

											
										
										
											2022-05-30 15:49:31 -07:00
+								{{ partial "processed-content.html" . }}
-												Refactor: add webring data from a CSV

The webring list was getting repetitive.

											
										
										
											2022-03-15 13:45:21 -07:00
+								{{ partial "posts.html" . }}
 								{{ partial "webrings.html" . }}
-												Refactor to make more body text narrow

Now more text should fall within WCAG limits.

											
										
										
											2022-07-11 17:20:36 -07:00
+								</div>
-												Add missing <main> landmark

											
										
										
											2022-05-01 21:04:49 -07:00
+								</main>
-												Batman!! (this commit has no parents)

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.

											
										
										
											2020-11-03 15:46:20 -08:00
+								{{ end }}