seirdy.one/layouts/posts/single.html

{{- define "main" -}}
{{- $canonicalRelPermalink := .RelPermalink | replaceRE "^/~seirdy/" "/" }}
{{- .Scratch.Set "codeIndex" 1 -}}
<main itemprop="mainEntity" itemscope="" itemtype="https://schema.org/BlogPosting{{ if .Params.techarticle }} https://schema.org/TechArticle{{ end }}" itemid="{{ .Site.Params.CanonicalBaseURL }}{{ $canonicalRelPermalink }}">
	<link itemprop="isPartOf" href="{{ .Site.Params.CanonicalBaseURL }}/" />
	{{ partial "full-article.html" . }}
	{{ partial "webmentions.html" . }}
</main>
{{ partial "prev-next.html" . -}}
{{- end }}
More markup formatting, remove unnecessary div - Decrease the article dom depth by 1 by replacing <main><div> with just <main>. - Fix some whitespace so the HTML output looks better. 2022-04-25 17:28:13 -07:00			`{{- define "main" -}}`
Microdata: add itemid attributes 2022-05-06 10:33:42 -07:00			`{{- $canonicalRelPermalink := .RelPermalink \| replaceRE "^/~seirdy/" "/" }}`
More markup formatting, remove unnecessary div - Decrease the article dom depth by 1 by replacing <main><div> with just <main>. - Fix some whitespace so the HTML output looks better. 2022-04-25 17:28:13 -07:00			`{{- .Scratch.Set "codeIndex" 1 -}}`
Microdata: fix relative urls, add a11y metadata - 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. 2022-06-29 17:54:51 -07:00			`<main itemprop="mainEntity" itemscope="" itemtype="https://schema.org/BlogPosting{{ if .Params.techarticle }} https://schema.org/TechArticle{{ end }}" itemid="{{ .Site.Params.CanonicalBaseURL }}{{ $canonicalRelPermalink }}">`
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			`<link itemprop="isPartOf" href="{{ .Site.Params.CanonicalBaseURL }}/" />`
Internal: re-org templates a bit 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. 2022-04-27 08:44:13 -07:00			`{{ partial "full-article.html" . }}`
			`{{ partial "webmentions.html" . }}`
More markup formatting, remove unnecessary div - Decrease the article dom depth by 1 by replacing <main><div> with just <main>. - Fix some whitespace so the HTML output looks better. 2022-04-25 17:28:13 -07:00			`</main>`
Add prev/next post navigation links Also adjust some margins to eliminate cut-off elements. 2022-05-18 17:21:48 -07:00			`{{ partial "prev-next.html" . -}}`
			`{{- end }}`