docs: design author profiles (ADR 0002 + glossary)

Capture the decision to enrich author taxonomy term pages with opt-in
profile content files, keeping the display name as the frontmatter key
with an optional preferred-name override (X over Y).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

Author: HeyItsGilbert

CONTEXT.md

@@ -13,3 +13,22 @@ and used as a site section, "Module" means specifically these org-stewarded proj
 — not the generic sense of "any PowerShell module you `Install-Module`", which is the
 subject of the site as a whole.
 _Avoid (for this concept)_: project, tool, package
+
+**Author**:
+A person credited as a contributor to site content (articles, podcast episodes) via
+the `authors:` frontmatter. Each distinct Author is surfaced as a taxonomy term with
+its own profile page, and may optionally describe themselves (avatar, tagline, bio,
+links). An Author exists the moment they are credited on a piece of content; the
+self-description is optional enrichment, not what makes someone an Author.
+_Avoid (for this concept)_: contributor, writer, user, account
+
+The **author name** stored in `authors:` frontmatter is both the display byline and
+the source of the Profile URL slug — it is the stable key. An Author may additionally
+set a **preferred name** on their Profile, which overrides only how their name is
+*displayed*; it never changes the slug or the byline key. Authors without a Profile
+display their author name unchanged.
+
+**Profile**:
+The per-Author page at `/authors/<name>/` listing that Author's content and, when
+provided, their self-description. Distinct from the **Author list** — the index page
+at `/authors/` showing every Author as a card.

docs/adr/0002-author-profiles.md

@@ -0,0 +1,45 @@
+# Author profiles: enrich taxonomy term pages, keep the display name as the key
+
+Authors are a Hugo taxonomy derived from the `authors:` frontmatter on ~1,045 articles
+and podcast episodes (see [[Author]] in `CONTEXT.md`). The term pages at `/authors/<name>/`
+are auto-generated and show only a name and a content list. To let an Author describe
+themselves (avatar, tagline, bio, links), we enrich each term page with an **optional**
+content file at `content/authors/<slug>/_index.md`. Profiles are **opt-in via PR** — not
+pre-scaffolded — so most Authors have no file and must keep rendering correctly.
+
+The load-bearing decision is what gets stored in every article's `authors:` frontmatter.
+We keep the **display name** there (`authors: [James Petty]`), exactly as today. The name
+is both the byline and the source of the Profile slug — the stable key. A Profile may set
+a **preferred name** that overrides only how the name is *displayed*; it never changes the
+slug or the byline. Authors without a Profile render their author name unchanged.
+
+## Considered options
+
+- **Slug as the key** (`authors: [james-petty]`, display name rendered from the Profile) —
+  rejected. It decouples slug from name, but the display name would then live *only* in the
+  Profile. With ~70 of 80 Authors un-enriched at launch, their bylines and cards would fall
+  back to a humanized slug — `darren-mar-elia` → "Darren Mar Elia" (wrong hyphen),
+  `jasonmorgan` → "Jasonmorgan". It also forces a repo-wide migration of all 1,045 files.
+- **Display name as the key, with an optional preferred-name override** — chosen. Zero
+  migration, correct bylines for every Author for free, and the changeable-display-name
+  benefit is preserved for those who opt in. The only thing it gives up is a slug decoupled
+  from the original name — but the slug is a URL we want stable anyway, and renaming it is a
+  redirect-and-find/replace job in *either* model.
+
+A central `data/authors.yaml` was also rejected in favor of taxonomy term content files:
+term files bind to the existing `/authors/<name>/` page automatically and carry a Markdown
+bio, which a data file cannot do naturally.
+
+## Consequences
+
+- The profile content file's directory **must** equal Hugo's slug of the exact author
+  string; a mismatch yields an orphan page that enriches nothing. A `new-author.ps1`
+  scaffolder generates the file with the right slug, and a build-time check flags author
+  content files whose slug matches no taxonomy term.
+- Renaming a slug is the rare, deliberate case: `new-author.ps1` rewrites the term across
+  content and adds an `aliases` redirect on the Profile to preserve the old URL.
+- Avatars resolve `avatar` → `gravatar_hash` → `email` → `identicon` fallback. Raw `email`
+  is convenient but lands in the public repo; `gravatar_hash` lets the privacy-conscious
+  avoid that, and an explicit `avatar` image bypasses Gravatar entirely.
+- The Author list orders enriched profiles first, then by count, so a partially-filled grid
+  reads as intentional rather than sparse.