Content

A page is a Markdown file of a bundle (site.md): its front matter in Lima between --- lines, then its text in Markanto. Content is untrusted: hadley writes what it says escaped, and a page cannot make hadley read outside its bundle or write outside the site’s output.

Title

A page’s title is its front matter’s title or, without one, the first block of its text when it is a # heading; the bold line right after that heading (__Subtitle__) is then its subtitle, unless the front matter has one. A heading or bold line that is the title or subtitle is taken out of the text, so the page shows it once. A page with both a title and such a heading gives its title twice: that is a problem, which stops a publish build of the page. An empty title is a problem too. linktext is the shorter name navigations and llms.txt show for a page; without it, they show its title.

Front matter

---
publishFrom: 2026-11-02
description: How this site began.
cover: desk.jpg
category: notes
tags: [beginnings, tools]
author: $(persons/ada)
---

config.lima may declare more fields for its theme, and the values a field may have (config.md, “Fields of a page”). Any other field is a problem of the page; so is a value of the wrong kind, such as a date that is no date.

Notes

A note (notes/, site.md) is a short dated page, written and built as any page: its title, a few lines of text, its publishFrom and its description, the line a list shows of it. Where it points somewhere else, link is that address, as on any page: https, and on another site, as a page of this one is linked by its id in the text ($id). Its kind is its category and its groups are its tags, with the values config.lima allows (config.md, “Fields of a page”).

---
publishFrom: 2026-11-04
category: issue
tags: [staticcheck, go]
link: https://github.com/dominikh/go-tools/issues/1847
description: staticcheck skips every package under the user cache directory, taking it for Go's build cache.
---
# staticcheck ignores its config under ~/.cache

Reported with a script that plays every case; the suggestion is to compare against `GOCACHE` instead.

A note without a publishFrom is a problem of the note. On any page, link is read as a link in the text is: a destination the text may not have is refused, and so are whitespace and control characters, a scheme other than https and an origin of this site in any of its languages, a trailing dot of its host included. The page keeps the address as it parses, and .hadley/links.json lists it with the text’s external links. A note that stands alone as a .md file has no bundle, so a file it names is a problem; a note with files is a bundle, as an article is. Templates list the notes as noteList (themes.md, “Notes”); the home page’s list and the feed name none.

Markanto in hadley

hadley reads Markanto as its specification says. What it adds:

Links. [text]($about) links the page with the id about in the language of the page that links it; [text]($about#team) a section of it. A page that is not published is no link target: its link is left out of a published page, and marked in a dev build. A link to another site uses http, https, mailto or tel; a link to a file of the bundle names it, relative, [the paper](paper.pdf), and hadley publishes it unchanged; an HTML, XHTML, XML or MHTML file it refuses (SECURITY.md).

Pictures. ![A desk by a window](desk.jpg) is a picture of the bundle, made in the widths and formats the page’s template asks for, with its alt text as written; a picture that takes longer than 60 seconds to make stops the build. <m …> around a picture sets how it is shown:

A picture labelled as AI-generated in its metadata (XMP) carries the theme’s label and an alt text that says so.

The pictures hadley publishes say nothing of where they were taken. One made in widths keeps its colour profile, its XMP and, of its EXIF, who made it and who holds its rights: no location, camera or serial number, and the XMP loses its location too, as a position or as a place by name (a city, a country); it stands upright, as its camera meant. A JPEG or PNG copied as it is (native, linked, or sized in the text) loses the same, its IPTC its places by name, its pixels as they are and of its EXIF only the orientation and the rights. Another kind of picture, a WebP or AVIF say, that carries EXIF or a location fails the build, since hadley cannot take them out of it. <m data-exif=keep> around a picture publishes all of it, location included, where that is wanted, as for a photo with its camera settings. The build says how many pictures it published without their location; the file in the bundle stays as it is.

Drawings. <m data-svg=inline>![Right answers by method](accuracy.svg)</m> writes an SVG of the bundle into the page instead of an <img>, so that it takes its colours from the theme (themes.md, “Drawings”). A drawing stands as a block, with a caption if it has one; its data-size goes on its figure as written, for the theme to read (native: at the drawing’s own width), and data-style does not apply. If accuracy.narrow.svg lies beside it, the page holds both, and the theme shows the one that fits the width. On a wide screen a click enlarges a drawing; Esc or a click beside it closes it. The file itself is published as well, as the page’s Markdown twin names it.

A drawing is content, and content is untrusted. It may hold shapes (path, rect, circle, ellipse, line, polyline, polygon), text (text, tspan), g, defs, title, desc, use, gradients, clip paths, masks and markers, with their geometry and presentation attributes, id, role, aria-label, aria-labelledby, aria-describedby, aria-description, aria-roledescription, aria-hidden, and as class only the theme’s fig- classes (themes.md, “Drawings”). Its text is set in the page’s font, or in one a fig- class of the theme gives it, at the size, weight and style it gives; its own font-family names only generic families, unquoted (monospace, sans-serif, serif, system-ui, ui-monospace, ui-sans-serif, ui-serif), which load no file and serve the file seen on its own. A title or desc holds only text, a shape only a title or desc. A presentation value may call colour, arithmetic and transform functions, and name nothing but an #id of the same file (url(#id), <use href="#id">); an id is a letter or _, then letters, digits, _ and -. Anything else stops the build, with the file and the line: a script, an event attribute, <style>, a style attribute, <foreignObject>, <image>, a link, a URL, a font of its own, var(), a backslash or a CSS comment in a value, a DOCTYPE or an entity. hadley leaves out only comments, the XML declaration and the SVG namespaces, which a page does not need, and the root’s role, aria-label, aria-labelledby and aria-hidden: the alt text names the drawing. It gives the ids of each drawing a prefix of their own with a ., which no other id of the page has. A drawing over 32 KB (32,768 bytes) is reported.

Media. <m video preview=poster.jpg>[The walk](walk.mp4)</m> shows a video with its poster, <m audio> a sound with its picture; <m embed>[Demo](https://example.com/embed)</m> an embed over https.

Blocks. A container names what it is, after its fence and a space: ::: loud sets a passage apart, ::: tldr is a summary at the top, and ::: nocount holds text the reading time and the character count leave out.

::: tldr
The short version.
:::

Headings get an id from their text, or the one written after them (## Team {#team}), and the theme’s heading template (themes.md, “Headings”). Footnotes stand after the paragraph that names them. Code in a block that names its language is highlighted (highlighting.md). With typography: enabled: true, quotes, dashes and ellipses are set as the page’s language sets them.