Enrich author profiles and link glossary contributors

Ouverte
#862 1 commentaire 0 réactions 1 personne assignée Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

@richarddushime y travaille déjà.

Depuis le 25/8/2026.

Évaluation

Cette issue n'a pas encore été évaluée.

Description

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.
Langage dominant
HTML
Étoiles
42
Forks
33
Merge moyen
16 h 3 min
PR mergées (30 j)
121

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de forrtproject/forrtproject.github.io

Toutes les issues de forrtproject/forrtproject.github.io

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.