seirdy.one/layouts/_default/baseof.html

<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" lang="{{- default "" .Site.LanguageCode }}" xml:lang="{{- default "" .Site.LanguageCode }}" prefix="og: https://ogp.me/ns# article: https://ogp.me/ns/article# cc: http://creativecommons.org/ns#">
{{ partial "head.html" . -}}
<body itemscope="" itemtype="https://schema.org/WebPage">
{{ partial "header.html" . -}}
{{- block "main" . }}{{- end -}}
{{ partialCached "footer.html" . }}
</body>
</html>
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			`<!DOCTYPE html>`
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			`<html xmlns="http://www.w3.org/1999/xhtml" lang="{{- default "" .Site.LanguageCode }}" xml:lang="{{- default "" .Site.LanguageCode }}" prefix="og: https://ogp.me/ns# article: https://ogp.me/ns/article# cc: http://creativecommons.org/ns#">`
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			`{{ partial "head.html" . -}}`
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			`<body itemscope="" itemtype="https://schema.org/WebPage">`
Fix caching 2022-05-01 13:36:02 -07:00			`{{ partial "header.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			`{{- block "main" . }}{{- end -}}`
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			`{{ partialCached "footer.html" . }}`
Indieweb: structured data for rest of website Outside the blogposting, add addl. structured data for the surrounding site: the license, copyright holder, navigation items, source code link, etc. 2022-02-10 22:12:45 -08:00			`</body>`
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			`</html>`