Enrich author profiles and link glossary contributors

Aperta
  • Qualcosa non va?
#862 1 commento 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@richarddushime ci sta già lavorando.

Dal 25/8/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

content related enhancement new website

Why this needs addressing

Many author profiles are effectively name-only records. For example, content/authors/kimberly-quinn/_index.md contains no role, biography, affiliation, or verified external profile, and the live page is a minimal profile with generic metadata. Meanwhile glossary pages contain named drafters and reviewers, but those names are not consistently linked to profile entities.

The site already has useful structured-data and author-linking partials, so this is an opportunity to connect existing attribution rather than invent new content.

Requested change

  • Establish a data-completeness workflow for author records: add a verified name, role/affiliation, biography, and external identifiers only when supplied or confirmed by the contributor.
  • Add ORCID when verified; emit it in sameAs and visible profile content, without guessing or fabricating identifiers.
  • Link glossary drafted-by, reviewed-by, translated-by, and translation-reviewed-by names to matching author pages using a stable mapping rather than fragile display-name slugification.
  • Keep genuinely empty/unverified profiles noindexed until they contain useful content.

Acceptance criteria

  • A representative set of glossary contributor names resolves to the correct author profile where one exists.
  • Verified ORCIDs appear visibly and in Person JSON-LD sameAs.
  • Empty profiles are not promoted to indexable thin pages.
  • Add a report or build check for contributor names that cannot be resolved.
Lingua principale
HTML
Stelle
42
Fork
33
Merge medio
17h 18m
PR unite (30g)
111

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di forrtproject/forrtproject.github.io

Tutte le issue di forrtproject/forrtproject.github.io

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.