Idea, not a defect — worth discussing before anyone builds it.
lib/speakers.ts now holds enough for a page of its own: name, url, sameAs, image. The talk history is derivable by scanning events/ for each registry key, and per-event worksFor / jobTitle / bio give each entry in that history its point-in-time context.
A /speakers/{key} page would:
- give the hero byline and the speaker block somewhere to link, instead of pointing straight off-site to LinkedIn
- surface repeat speakers — several people have given three or more talks, which nothing on the site currently shows
- add a real SEO surface, with
Person structured data and sameAs back to the profiles
Open questions
- Only for speakers with 2+ talks, or all 26 registry entries?
- Include the YouTube recording per talk where
youtube: exists?
- Needs
generateStaticParams over the registry plus a reverse index (event → speakers) in lib/events-server.ts.
Came out of adding the speaker byline and block (components/event-speakers.tsx).
Idea, not a defect — worth discussing before anyone builds it.
lib/speakers.tsnow holds enough for a page of its own:name,url,sameAs,image. The talk history is derivable by scanningevents/for each registry key, and per-eventworksFor/jobTitle/biogive each entry in that history its point-in-time context.A
/speakers/{key}page would:Personstructured data andsameAsback to the profilesOpen questions
youtube:exists?generateStaticParamsover the registry plus a reverse index (event → speakers) inlib/events-server.ts.Came out of adding the speaker byline and block (
components/event-speakers.tsx).