Replace Event.performer placeholder with real keynote speakers
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- hugo
- Domain
- web-dev
Research direction
Start in layouts/partials/structured-data.html and compare its Event schema with the existing template in structured-data-speakers.html. Check data/speakers.yml to determine whether keynote speakers are confirmed; the Event schema should either list those speakers or omit performer when none are confirmed.
Written by the indexing model from the issue text.
Description
Problem
The Event schema on the homepage has a generic placeholder for performer:
```json
"performer": {
"@type": "Organization",
"name": "Python Community Speakers"
}
```
Google uses performer to surface speaker rich results. This placeholder adds no value and may be flagged during structured data review.
Fix
Once keynote speakers are confirmed in data/speakers.yml, replace the placeholder with a Hugo range over keynote speakers (the template already exists in structured-data-speakers.html):
```go
"performer": [
{{ range where .Site.Data.speakers "keynote" true }}
{
"@type": "Person",
"@id": "{{ $.Site.BaseURL }}speakers/#{{ .id }}",
"name": "{{ .name }}"
},
{{ end }}
]
```
Until keynote speakers are confirmed, the performer field should be removed from the Event schema entirely rather than using a placeholder.
Files to change
layouts/partials/structured-data.html
- Dominant language
- HTML
- Stars
- 1
- Forks
- 0
- Avg merge
- 10m
- Merged PRs (30d)
- 1
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from PythonIreland/2026.pycon.ie
-
priority: low seo
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
content priority: medium
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
priority: low
Difficulty 1/5 Under an hour Newbie friendliness 86/100
-
enhancement priority: medium seo
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug priority: medium seo
Difficulty 1/5 Under an hour Newbie friendliness 88/100
All issues in PythonIreland/2026.pycon.ie
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
[Block] Latest Posts [Type] Bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
gitbutlerapp/gitbutler#15998 · 1 comment ·
-
t/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
task
Difficulty 2/5 1-3 hours Newbie friendliness 86/100