jwogrady Working notes on tools, and why they earn their place

Front matter that the index depends on

The theme carries no content types. What an entry is comes entirely from its front matter, and three fields are load-bearing: an entry missing them renders correctly and appears nowhere.

The three that matter

tags     = ["hugo", "workflow"]
archives = ["2026", "2026-09", "2026-09-20"]
resolves = "JRN 26-007"
aliases  = ["/r/26-007/"]

tags are subjects, not decoration. Frequency sets each tag’s colour in the index, so a table of fifty entries is legible as a field before a word is read. This only works if terms are reused — a new tag per entry gives fifty identical grey labels. Reuse what exists; invent sparingly.

archives builds the date index. It is not derived from date — the three-element year / month / day form has to be written out, and the archetype does it automatically. Wrong here means the entry is missing from /archives/ while looking fine on its own page.

resolves + aliases are the citation handle. Assigned once, never renumbered, resolving at /r/<code>/ forever. Two entries claiming the same number is a silent collision — one alias wins and the other is lost.

The optional ones worth using

description = 'One sentence. Used for meta description and search results.'
claim       = 'One line. Renders as the standout paragraph under the date.'

Images, in a bundle

[[resources]]
  src   = "screenshot.png"
  title = "Screenshot"
  [resources.params]
    alt     = "What is actually in the image, for a reader who cannot see it."
    caption = "Rendered under the figure."
    credit  = "Screenshot"

alt is not optional. The theme prints caption and credit beneath the figure and uses alt on the image itself.