Enrich author profiles and link glossary contributors

Aberta
#862 1 comentário 0 reações 1 responsável Ver no GitHub

Mantenedores costumam responder em até 1 dia

@richarddushime já está trabalhando nisso.

Desde 25/8/2026.

Avaliação

Esta issue ainda não foi avaliada.

Descrição

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.
Linguagem predominante
HTML
Estrelas
42
Forks
33
Merge médio
16h 3min
PRs com merge (30d)
121

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de forrtproject/forrtproject.github.io

Todas as issues de forrtproject/forrtproject.github.io

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.