@heroiclands/package-build 23.13.0 → 24.0.1

package/hugo-theme/layouts/partials/draft-state.html

@@ -1,26 +0,0 @@
-{{- /*
-  Whether a page's note is an unfinished draft.
-
-  The `draft` tag is the authored signal, and it is the only one either side
-  can read: the content build asks it through its own single reader
-  (package-build/engine/note-vocabulary.mjs, `DRAFT_TAG`) and a theme cannot
-  import that, so the shared fact is the tag itself. It reaches the page
-  because the build copies a note's own front matter onto it.
-
-  It is spelled once, here. Two partials act on the state — the tag row leaves
-  it out of a page's subjects, and the notice states it — and a second literal
-  is how the two come apart.
-
-  Hugo's own reserved `draft: true` is a different thing entirely and is never
-  written by the build: a page carrying it is not rendered at all.
-
-  Context: the page. Returns "true" for a draft and "" for anything else, which
-  is what `if` reads.
-*/ -}}
-{{- $draft := false -}}
-{{- range .Params.tags -}}
-  {{- if eq (lower .) "draft" -}}
-    {{- $draft = true -}}
-  {{- end -}}
-{{- end -}}
-{{- return $draft -}}

package/hugo-theme/layouts/partials/header.html

@@ -1,35 +0,0 @@
-<header class="site-header" data-pagefind-ignore>
-  <div class="header-inner">
-    <a href="{{ .Site.Home.RelPermalink }}" class="site-title">
-      {{- with .Site.Params.brand }}{{ with .logo }}
-      <img src="{{ partial "cdn-url.html" (dict "site" $.Site "path" .) }}" alt="Heroic Lands" class="site-logo">
-      {{- end }}{{ end }}
-      <span class="title-main">Heroic Lands</span>
-    </a>
-    <div class="header-actions">
-      <nav class="site-nav">
-        {{ range .Site.Menus.main }}
-          {{ if .HasChildren }}
-            <div class="nav-dropdown">
-              <a href="{{ .URL }}" class="nav-link{{ if $.IsMenuCurrent "main" . }} active{{ end }}">
-                {{ .Name }}
-                <svg class="dropdown-arrow" width="10" height="6" viewBox="0 0 10 6" fill="currentColor"><path d="M1 1l4 4 4-4"/></svg>
-              </a>
-              <div class="dropdown-menu">
-                {{ range .Children }}
-                  <a href="{{ .URL }}" class="dropdown-item">{{ .Name }}</a>
-                {{ end }}
-              </div>
-            </div>
-          {{ else }}
-            <a href="{{ .URL }}" class="nav-link{{ if $.IsMenuCurrent "main" . }} active{{ end }}">{{ .Name }}</a>
-          {{ end }}
-        {{ end }}
-      </nav>
-      {{ partial "search.html" . }}
-      <button class="nav-toggle" aria-label="Toggle navigation">
-        <span></span><span></span><span></span>
-      </button>
-    </div>
-  </div>
-</header>

package/hugo-theme/layouts/partials/hero-banner.html

@@ -1,85 +0,0 @@
-{{- /*
-  Hero banner partial.
-
-  Displays a full-width banner band (using the same .hero.hero-with-image
-  classes as the homepage) with a centered page title and description
-  above the content.
-
-  Every path below resolves through cdn-url.html against the consuming
-  site's `params.cdnBaseURL`; the theme names no host of its own.
-
-  The resolution itself lives in `banner-url.html`, which a derived landing card
-  calls too. The order is documented in both places because this is where a
-  reader looking at a banner starts; that partial is where it happens.
-
-  Banner image resolution order:
-    1. .Params.data.banner         — a note's own hero image, which the content
-                                     build resolved from an asset Address into
-                                     the address its asset host serves. Used
-                                     exactly as given. A blank declines a hero
-                                     image; unset or `null` carries on.
-    2. .Params.banner              — a hand-authored page's value. `none` (or
-                                     `false`) declines a hero image entirely —
-                                     see "Declining" below. A full URL is used
-                                     as-is; anything else is treated as a
-                                     fragment under images/.
-    3. images/banners/{name}.webp  — the default for the page's kind: the
-                                     banner data/banner-kinds.yaml maps its
-                                     type and subType to, or its category for
-                                     type=doc pages
-    4. images/banners/default.webp — used when the page has no type, *and*
-                                     whenever the name picked by 2 or 3 is not
-                                     in the declared inventory (see below).
-
-  Existence, and why step 4 is a declaration rather than a test.
-  The image is served from the consumer's asset host, and Hugo cannot ask a
-  remote host whether a URL exists — so a name that was never drawn would be
-  emitted unchecked and 404 in silence, the band rendering with its title,
-  palette and gradient intact behind a dead URL. `data/banners.yaml`
-  is the declaration that stands in for the test it cannot make: a resolved name
-  absent from `available` falls back to `fallback` and warns once. That file
-  documents how the list is kept honest (`npm run lint:banners` fetches every
-  name and fails on a non-200), and a consumer publishing its own artwork set
-  overrides the whole list by shipping its own `data/banners.yaml`.
-
-  The check applies only to a *relative* path resolving directly inside the
-  declared banner directory. An absolute URL, and a fragment pointing anywhere
-  else under images/, pass through untouched: the theme has no inventory for
-  either and must not second-guess an address it cannot know about. A step 1
-  address is not checked either — the build resolved it against a real asset
-  record, so the question has already been answered.
-
-  Declining a hero image.
-  `banner: none` on a hand-authored page, and a blank `data.banner` on a note,
-  render the band with no image at all — the title, the palette
-  and the .hero-with-image gradient, which is what gives the band its presence.
-  This is not the same as having no banner yet: a package may have a standing
-  editorial reason to publish no imagery, and the fan-material carve-outs do.
-  Falling back to a default for them would substitute artwork where the
-  considered answer was "none", so declining has to be sayable.
-*/ -}}
-
-{{- /* The order above, the `none` decision, the type-to-banner mapping in
-       `data/banner-kinds.yaml` and the declared-existence check all live in
-       `banner-url.html`, which a derived landing card calls too. A hero band
-       always wants the default for its page's kind; a card never does. A page
-       with no type gets `default`. */ -}}
-{{- $type := .Params.type | default "" -}}
-{{- $bannerURL := partial "banner-url.html" (dict
-    "site" .Site
-    "data" .Params.data
-    "banner" .Params.banner
-    "type" $type
-    "subType" .Params.subType
-    "category" .Params.category
-    "subtype" (cond (eq $type "") "default" "")
-    "context" .RelPermalink) -}}
-
-<section class="hero hero-with-image"{{ with $bannerURL }} style="background-image: url('{{ . }}');"{{ end }}>
-  <div class="hero-inner" data-pagefind-ignore>
-    <h1>{{ .Title }}</h1>
-    {{- with .Params.description }}
-    <p class="hero-tagline">{{ . }}</p>
-    {{- end }}
-  </div>
-</section>

package/hugo-theme/layouts/partials/infobox/entry.html

@@ -1,18 +0,0 @@
-{{- /*
-  One entry of a `runin` group or a `list` section.
-
-  An entry is `{lead, text, url}`. It links when the build reached the page it
-  names, and keeps its words when it did not — a panel naming something this
-  site does not publish is better than a panel silently one entry short.
-  `lead`, where present, is plain text set before the link, so a line such as
-  a membership links the body's name and nothing else.
-
-  Takes `entry` and the `class` its medium gives it.
-*/ -}}
-{{- $entry := .entry -}}
-{{- with $entry.lead }}{{ . }}{{ end -}}
-{{- with $entry.url -}}
-<a class="{{ $.class }}" href="{{ . }}">{{ $entry.text }}</a>
-{{- else -}}
-<span class="{{ $.class }}">{{ $entry.text }}</span>
-{{- end -}}

package/hugo-theme/layouts/partials/infobox/items.html

@@ -1,26 +0,0 @@
-{{- /*
-  What one infobox section holds, whatever its layout.
-
-  A section carries its content under the key its layout names — `rows`,
-  `cells`, `groups` or `entries` — so one lookup answers "is there anything to
-  draw?" for every layout there is. Returns a slice, empty when there is
-  nothing.
-
-  Takes the section. Returns the items.
-
-  An unrecognised layout returns nothing and says so once: the four layouts
-  are a closed set, so a fifth means this theme is older than the content it
-  is drawing, and a silently dropped section is the expensive way to find out.
-*/ -}}
-{{- $section := . -}}
-{{- $layout := $section.layout | default "" -}}
-{{- $key := index (dict "rows" "rows" "grid" "cells" "runin" "groups" "list" "entries") $layout -}}
-{{- $items := slice -}}
-{{- with $key -}}
-  {{- with index $section . -}}
-    {{- $items = . -}}
-  {{- end -}}
-{{- else -}}
-  {{- warnidf "infobox-unknown-layout" "infobox: section layout %q is not one of rows, grid, runin or list, so the section is not drawn. Upgrade @heroiclands/hugo-theme to a version that draws it." $layout -}}
-{{- end -}}
-{{- return $items -}}

package/hugo-theme/layouts/partials/infobox/section.html

@@ -1,56 +0,0 @@
-{{- /*
-  One infobox section, arranged the way its `layout` says.
-
-  Four layouts, a closed set, and the key a section carries its content under
-  is what names it:
-
-    rows   — label/value pairs, one per line          `rows`
-    grid   — short label/value cells packed together  `cells`
-    runin  — groups of comma-joined entries           `groups`
-    list   — one entry per line                       `entries`
-
-  Takes the section.
-
-  **A value of `0` is a value.** Armour that stops nothing edged is a fact
-  about the armour, so a cell is printed as it comes rather than guarded with
-  `with`, which would drop a zero along with an absence.
-*/ -}}
-{{- $section := . -}}
-{{- $layout := $section.layout | default "" -}}
-{{- if eq $layout "rows" -}}
-<dl class="info-profile-grid">
-  {{- range $section.rows }}
-  <dt>{{ .label }}</dt>
-  <dd>{{ partial "infobox/value.html" . }}</dd>
-  {{- end }}
-</dl>
-{{- else if eq $layout "grid" -}}
-<div class="info-attrs-grid">
-  {{- range $section.cells }}
-  <div class="info-attr">
-    <span class="attr-label">{{ .label }}</span>
-    <span class="attr-value">{{ .value }}</span>
-  </div>
-  {{- end }}
-</div>
-{{- else if eq $layout "runin" -}}
-  {{- range $section.groups }}
-  <p class="info-skill-line">
-    {{- with .label }}<span class="skill-cat">{{ . }}:</span>{{ end }}
-    <span class="skill-entries">
-      {{- range $i, $entry := .entries -}}
-        {{- if $i }}, {{ end -}}
-        {{- partial "infobox/entry.html" (dict "entry" $entry "class" "skill-entry") -}}
-      {{- end -}}
-    </span>
-  </p>
-  {{- end }}
-{{- else if eq $layout "list" -}}
-<ul class="info-mystical-list">
-  {{- range $section.entries }}
-  <li class="info-mystical-item">
-    {{- partial "infobox/entry.html" (dict "entry" . "class" "mystical-name") -}}
-  </li>
-  {{- end }}
-</ul>
-{{- end -}}

package/hugo-theme/layouts/partials/infobox/value.html

@@ -1,43 +0,0 @@
-{{- /*
-  One row's value, drawn by its `kind`.
-
-  Five kinds, a closed set:
-
-    text   — a string
-    number — a number
-    link   — `{text, url}`
-    links  — a list of those, comma-joined
-    list   — a list of strings, comma-joined
-
-  Takes the row.
-
-  **A value of `0` is a value**, so a number is printed as it comes rather
-  than guarded with `with`, which would drop a zero along with an absence.
-  Anything the build did not classify is set as text, which is what an
-  unlabelled scalar is.
-*/ -}}
-{{- $kind := .kind | default "text" -}}
-{{- if eq $kind "link" -}}
-  {{- partial "infobox/entry.html" (dict "entry" .value "class" "info-link") -}}
-{{- else if eq $kind "links" -}}
-  {{- range $i, $entry := .value -}}
-    {{- if $i }}, {{ end -}}
-    {{- partial "infobox/entry.html" (dict "entry" $entry "class" "info-link") -}}
-  {{- end -}}
-{{- else if eq $kind "list" -}}
-  {{- delimit .value ", " -}}
-{{- else if eq $kind "number" -}}
-  {{- /* A whole number is grouped, so a population reads as 500,000 rather
-         than as a run of digits a reader has to count. Grouping is
-         typography and belongs to the medium; the number itself is the
-         build's. Anything that is not a plain integer — a measurement, or a
-         value the build did not classify — is set as written. */ -}}
-  {{- $digits := printf "%v" .value -}}
-  {{- if findRE `^-?[0-9]+$` $digits -}}
-    {{- lang.FormatNumberCustom 0 (int $digits) -}}
-  {{- else -}}
-    {{- .value -}}
-  {{- end -}}
-{{- else -}}
-  {{- .value -}}
-{{- end -}}

package/hugo-theme/layouts/partials/infobox.html

@@ -1,57 +0,0 @@
-{{- /*
-  The infobox rail — every box a page declares, drawn in the order declared.
-
-  **The content is not decided here.** A page's `infoboxes:` front matter
-  carries an ordered list of boxes, each holding ordered sections, each holding
-  ordered rows, cells, groups or entries, already labelled. This partial and
-  the three under `infobox/` switch on a section's `layout` and a value's
-  `kind` and on nothing else — never on a note type, never on a field name.
-  That is what lets a field added to a type appear here with no edit.
-
-  A box is a `<details>` disclosure, open by default: native, accessible, and
-  no JavaScript. It is what lets several boxes stack for nothing — a note box
-  and one box per system are three summary lines when closed, rather than
-  three panels burying the prose.
-
-  Two kinds of box, and they answer emptiness differently:
-
-  - A **note box** with no section holding anything is not drawn. A heading
-    over nothing asserts a fact that is not there.
-  - A **system box** carries a `statement` where it has nothing to show, and
-    the statement is drawn in place of the sections. Which silence this is —
-    the system compiled no document, or it compiled one holding nothing the
-    profile has not already said — is decided by the build, because a reader
-    meeting one page cannot tell the two apart and neither can a template. A
-    system that does not map the note's type at all sends no box, and nothing
-    is drawn.
-
-  Returns an empty string when the page declares no box, so a caller can test
-  what comes back rather than reaching into the data itself.
-*/ -}}
-{{- range .Params.infoboxes -}}
-  {{- $box := . -}}
-  {{- $sections := slice -}}
-  {{- range $box.sections -}}
-    {{- if gt (len (partial "infobox/items.html" .)) 0 -}}
-      {{- $sections = $sections | append . -}}
-    {{- end -}}
-  {{- end -}}
-  {{- $system := eq ($box.kind | default "") "system" -}}
-  {{- if or $system (gt (len $sections) 0) }}
-<details class="info-sidebar info-box{{ with $box.id }} info-box-{{ . }}{{ end }}" open data-pagefind-ignore>
-  <summary class="info-sidebar-title"><h2>{{ $box.title }}</h2></summary>
-  {{- with $box.statement }}
-  <p class="info-statement">{{ . }}</p>
-  {{- else }}
-    {{- range $sections }}
-  <section class="info-section{{ with .id }} info-section-{{ . }}{{ end }}">
-    {{- with .label }}
-    <h3 class="info-section-title">{{ . }}</h3>
-    {{- end }}
-    {{ partial "infobox/section.html" . }}
-  </section>
-    {{- end }}
-  {{- end }}
-</details>
-  {{- end -}}
-{{- end -}}

package/hugo-theme/layouts/partials/page-body.html

@@ -1,152 +0,0 @@
-{{- /*
-  A note's body — the infobox rail, the content, and prev/next through its
-  catalog. Shared by `_default/single.html`, for a page, and `index.html`,
-  for the homepage note rendered as a page: the two are the same family, and
-  this is the shape they share. The caller renders the hero; this partial
-  starts at the article.
-
-  Context: the page.
-*/ -}}
-{{- /* The boxes a page declares, drawn by one generic renderer. What each box
-       holds is decided by the build and carried in `infoboxes:` front matter;
-       this file decides only where the rail goes. A page declaring none gets
-       back an empty string and no rail. */ -}}
-{{- $infobox := partial "infobox.html" . -}}
-{{- $hasSidebar := ne (trim $infobox " \r\n\t") "" -}}
-
-{{- /* The TOC partial only emits markup when the page has more than
-       3 H2 headings. To avoid laying the page out as a two-column
-       grid for nothing, detect the same condition here so we can
-       apply the `.single-with-toc` class conditionally. A page that
-       already has a rail gets its contents list at the foot of that
-       rail rather than a second column. */ -}}
-{{- $h2Count := len (findRE `(?m)^##\s+\S` (.RawContent | default "")) -}}
-{{- $hasToc := gt $h2Count 3 -}}
-
-{{- /* A draft page states it, which also decides the article's first grid
-       row — see the notice partial and `.single-with-notice`. */ -}}
-{{- $isDraft := partial "draft-state.html" . -}}
-
-<article class="single{{ if $hasSidebar }} single-with-sidebar{{ else if $hasToc }} single-with-toc{{ end }}{{ if $isDraft }} single-with-notice{{ end }}">
-  {{- /* A statement about the page rather than about its subject, so it leads
-         the article: above the rail and above the prose, at every width. It
-         spans the grid for that reason — inside `.single-content` it would sit
-         beside the boxes on a wide screen and below them on a narrow one,
-         where the rail comes first. */ -}}
-  {{ partial "draft-notice.html" . }}
-  {{- /* Filter values a search can narrow on, invisible and excluded from
-         indexing themselves — `data-pagefind-filter` is read wherever it
-         sits, `data-pagefind-body`/`data-pagefind-ignore` scoping included
-         (see the README's "Search" section). */ -}}
-  {{- with .Params.type }}<span data-pagefind-filter="type" hidden>{{ . }}</span>{{ end -}}
-  {{- with .Params.package }}<span data-pagefind-filter="package" hidden>{{ . }}</span>{{ end -}}
-  {{- if $hasSidebar }}
-  {{- /* The rail comes first in document order, because the infobox is
-         generated content prepended before the prose: on a narrow screen the
-         grid collapses and the boxes land where they were written, above the
-         text they summarise. */ -}}
-  <aside class="info-rail">
-    {{ $infobox }}
-    {{ if $hasToc }}{{ partial "toc.html" . }}{{ end }}
-  </aside>
-  {{- end }}
-  <div class="single-content">
-    {{- $tagChips := partial "tags.html" . -}}
-    {{- $beingSubtype := "" -}}
-    {{- if and (eq .Params.type "being") .Params.subType -}}
-      {{- $beingSubtype = cond (eq .Params.subType "npc") "NPC" (humanize .Params.subType) -}}
-    {{- end -}}
-    {{ if or .Params.date (ne (trim $tagChips " \r\n\t") "") $beingSubtype }}
-    <div class="single-meta">
-      {{ if .Params.date }}
-      <time class="single-date" datetime="{{ .Date.Format "2006-01-02" }}">{{ .Date.Format "January 2, 2006" }}</time>
-      {{ end }}
-      {{- with $beingSubtype }}<span class="single-subtype">{{ . }}</span>{{ end }}
-      {{ $tagChips }}
-    </div>
-    {{ end }}
-
-    <div class="single-body" data-pagefind-body>
-      {{ partial "dictionary-lists.html" .Content }}
-    </div>
-
-    {{ partial "related.html" . }}
-
-    {{- /*
-      Prev/next walk the page's own catalog, not its Hugo section (issue #48).
-      `.PrevInSection` / `.NextInSection` mean "the neighbouring page in this
-      directory", which was the same thing only while a page lived in a
-      directory named for its catalog. `@heroiclands/package-build`
-      (package-build#204) emits every content page flat under the content
-      mount, so a consumer's whole catalog is one section and these two links
-      would walk every page of every type — reading through the afflictions
-      silently left them.
-
-      So where a section holds more than one catalog, the sibling set is
-      narrowed to the pages sharing this page's catalog key. A section holding
-      a single catalog is left alone, because `.PrevInSection` already walks
-      exactly that catalog there — which is what makes this a no-op for a site
-      whose pages still sit in catalog-named directories. A page declaring no
-      catalog keeps the section-scoped result. The home page declares no
-      catalog and has no section siblings either way.
-
-      The catalog key: `type` for structured content, whose type *is* its
-      catalog (`affliction`, `skill`, `weapongear`, …); for `type: doc`, which
-      is prose rather than a catalog of its own, `subType` (what package-build
-      compiles from a note's classification) or, failing that, `category`
-      (what a documentation tree mounted from a repository directory
-      carries); "" for a page with no `type`, which has no catalog.
-
-      Ordering follows Hugo's: in a page collection `.PrevInSection` is the
-      *following* entry and `.NextInSection` the preceding one, so the
-      neighbours are taken at index+1 and index-1 respectively.
-    */ -}}
-    {{- $prev := .PrevInSection -}}
-    {{- $next := .NextInSection -}}
-    {{- $type := .Params.type | default "" -}}
-    {{- $key := $type -}}
-    {{- if eq $type "doc" -}}
-      {{- $key = .Params.subType | default (.Params.category | default "") -}}
-    {{- end -}}
-    {{- $siblings := slice -}}
-    {{- with .CurrentSection -}}
-      {{- if $key -}}
-        {{- $mixed := false -}}
-        {{- $matching := slice -}}
-        {{- range .RegularPages -}}
-          {{- $pageType := .Params.type | default "" -}}
-          {{- $pageKey := $pageType -}}
-          {{- if eq $pageType "doc" -}}
-            {{- $pageKey = .Params.subType | default (.Params.category | default "") -}}
-          {{- end -}}
-          {{- if eq $pageKey $key -}}
-            {{- $matching = $matching | append . -}}
-          {{- else if ne $pageKey "" -}}
-            {{- $mixed = true -}}
-          {{- end -}}
-        {{- end -}}
-        {{- if $mixed -}}{{- $siblings = $matching -}}{{- end -}}
-      {{- end -}}
-    {{- end -}}
-    {{- if $siblings -}}
-      {{- $index := -1 -}}
-      {{- range $i, $p := $siblings -}}
-        {{- if eq $p.Path $.Path -}}{{- $index = $i -}}{{- end -}}
-      {{- end -}}
-      {{- if ge $index 0 -}}
-        {{- $prev = "" -}}
-        {{- $next = "" -}}
-        {{- if lt (add $index 1) (len $siblings) -}}{{- $prev = index $siblings (add $index 1) -}}{{- end -}}
-        {{- if gt $index 0 -}}{{- $next = index $siblings (sub $index 1) -}}{{- end -}}
-      {{- end -}}
-    {{- end -}}
-    <nav class="single-nav">
-      {{ with $prev }}<a href="{{ .Permalink }}" class="nav-prev">&larr; {{ .Title }}</a>{{ end }}
-      {{ with $next }}<a href="{{ .Permalink }}" class="nav-next">{{ .Title }} &rarr;</a>{{ end }}
-    </nav>
-  </div>
-
-  {{ if and (not $hasSidebar) $hasToc }}
-    {{ partial "toc.html" . }}
-  {{ end }}
-</article>

package/hugo-theme/layouts/partials/related.html

@@ -1,138 +0,0 @@
-{{- /*
-  Related partial.
-
-  Renders a compact "Related" block at the bottom of a single page from the
-  page's `related` front matter, if it carries any.
-
-  Structure in front matter:
-    related:
-      seeAlso:   [{ title, url, type, gloss? }, ...] # deliberate references
-      backlinks: [{ title, url, type }, ...]   # pages that link here
-      mentions:  [{ title, url, type }, ...]   # pages this page links to
-
-  Rendering strategy:
-    - Render deliberate references in authored order, with their glosses.
-    - Merge both inferred directions into a single deduped pool (direction
-      doesn't matter to a reader — a connection is a connection).
-    - Group by the referenced page's `type`.
-    - Emit one labelled group per type, its entries laid out as a
-      CSS grid (`repeat(auto-fill, minmax(14em, 1fr))`) so a wide
-      screen shows two or three columns and a narrow one falls back
-      to a single column with no media query.
-    - The whole block is wrapped in a bordered, tinted card so it
-      visually sets off the end of the article.
-
-  Silent disappear: a page with no `related`, or whose lists are all
-  empty, emits nothing at all rather than an empty heading. The rows are
-  computed first and the <section> is rendered only when there is something
-  to put in it.
-
-  `return` cannot bail out early here. It sets the partial's
-  return value; it does not discard template text the partial has already
-  emitted, so a guard written that way still prints the empty shell. Hence
-  the emptiness test wraps the markup instead of preceding it.
-*/ -}}
-
-{{- /* `default dict` keeps the lookups below safe on a page with no
-       `related` at all, so the whole computation stays flat. */ -}}
-{{- $rel := .Params.related | default dict -}}
-{{- $seeAlso := or $rel.seealso slice -}}
-{{- $backlinks := or $rel.backlinks slice -}}
-{{- $mentions  := or $rel.mentions  slice -}}
-
-{{- /* Merge both directions, deduped by URL. `union` can't hash
-       slices of maps, so we walk the two lists in order and dedupe
-       by URL manually. Deliberate references take priority; mentions
-       precede backlinks among inferred connections. */ -}}
-{{- $seen := slice -}}
-{{- $merged := slice -}}
-{{- $deliberate := slice -}}
-{{- range $seeAlso -}}
-  {{- if not (in $seen .url) -}}
-    {{- $seen = $seen | append .url -}}
-    {{- $deliberate = $deliberate | append . -}}
-  {{- end -}}
-{{- end -}}
-{{- range $mentions -}}
-  {{- if not (in $seen .url) -}}
-    {{- $seen = $seen | append .url -}}
-    {{- $merged = $merged | append . -}}
-  {{- end -}}
-{{- end -}}
-{{- range $backlinks -}}
-  {{- if not (in $seen .url) -}}
-    {{- $seen = $seen | append .url -}}
-    {{- $merged = $merged | append . -}}
-  {{- end -}}
-{{- end -}}
-
-{{- /* Plural, human-readable label for each type. Falls back to
-       `humanize` for any type not listed here. */ -}}
-{{- $labels := dict
-  "affiliation"  "Affiliations"
-  "being"        "Beings"
-  "blog-post"    "Posts"
-  "character"    "People"
-  "continent"    "Continents"
-  "creature"     "Creatures"
-  "faith"        "Faiths"
-  "language"     "Languages"
-  "lore"         "Lore"
-  "organization" "Organizations"
-  "page"         "Pages"
-  "pantheon"     "Pantheons"
-  "people"       "Peoples"
-  "polity"       "Polities"
-  "project-page" "Projects"
-  "region"       "Regions"
-  "religion"     "Religions"
-  "settlement"   "Settlements"
-  "site"         "Places"
-  "world"        "Worlds"
--}}
-
-{{- /* Group refs by type, preserving alphabetical order within a
-       group (the input lists arrive already sorted). */ -}}
-{{- $groups := dict -}}
-{{- range $merged -}}
-  {{- $t := .type | default "page" -}}
-  {{- $existing := index $groups $t | default slice -}}
-  {{- $groups = merge $groups (dict $t ($existing | append .)) -}}
-{{- end -}}
-
-{{- /* Sort the group keys alphabetically by their rendered label
-       so the list reads A → Z regardless of insertion order. */ -}}
-{{- $rows := slice -}}
-{{- range $type, $refs := $groups -}}
-  {{- $label := index $labels $type | default (humanize $type) -}}
-  {{- $rows = $rows | append (dict "label" $label "type" $type "refs" $refs) -}}
-{{- end -}}
-{{- if $rows -}}
-  {{- $rows = sort $rows "label" "asc" -}}
-{{- end -}}
-
-{{- if or $rows $deliberate -}}
-<section class="related" aria-labelledby="related-heading" data-pagefind-ignore>
-  <h2 id="related-heading" class="related-heading">Related</h2>
-  {{- with $deliberate }}
-  <div class="related-group">
-    <h3 class="related-group-label">See also</h3>
-    <ul class="related-group-grid">
-      {{- range . }}
-      <li><a href="{{ .url }}">{{ .title }}</a>{{ with .gloss }} — {{ . }}{{ end }}</li>
-      {{- end }}
-    </ul>
-  </div>
-  {{- end }}
-  {{- range $rows }}
-  <div class="related-group">
-    <h3 class="related-group-label">{{ .label }}</h3>
-    <ul class="related-group-grid">
-      {{- range .refs }}
-      <li><a href="{{ .url }}">{{ .title }}</a></li>
-      {{- end }}
-    </ul>
-  </div>
-  {{- end }}
-</section>
-{{ end -}}