[JesperDramsch]

No description provided.

[JesperDramsch]

Routine review

Request. Title only, no body and no linked issue: "Fix apostrophe in PyCon Côte d'Ivoire entry". That covers one instance, the PyCon Côte d'Ivoire 2027 entry in _data/conferences.yml. The diff changes only its conference value, from a straight ' to a curly ’ (U+2019).

Checked against. Today is Mon Oct 19 12:37:16 UTC 2026 (date). I fetched no external URLs. Every claim below comes from the repository.

Needs your decision.

1. This PR was already merged at 2026-10-19T12:36:52Z (as aa1e44c) before this review ran, so any fix has to go in a follow-up PR. Where should the fix go? You can change the template, so that _layouts/conference.html:350,351,353,420 render {{ page.x | jsonify }} instead of '{{ page.x }}'. That covers every entry, now and later. Or you can change the data, adding U+2019 to place (and to the location title for consistency). That fixes only this entry. My recommendation is the template fix. It also makes the curly name optional. AGENTS.md says to spell conference the way the data already spells it, so whether to keep the curly name is your call.

Findings.

Important

• _data/conferences.yml:90 with _layouts/conference.html:353: the conference page for this entry still fails to run its script. The entry's place keeps the straight apostrophe (place: Abidjan, Côte d'Ivoire). Line 353 interpolates it unescaped as const confPlace = '{{ page.place }}';. That line sits in the same <script> element (lines 233–436) as the confName/seriesName lines (350, 420) that the curly name was meant to make parse. _config.yml's page_gen entry (data conferences, template conference) renders this record into that layout. The rendered snippet fails to parse:

  const confPlace = 'Abidjan, Côte d'Ivoire';
                                     ^^^^^^
  SyntaxError: Unexpected identifier 'Ivoire'
  

  The same snippet without that line, but with the curly confName, parses (node --check exit 0). So on /conference/…-2027/ the calendar-option handler and the follow/save button init still never run. Smallest fix: add | jsonify and drop the surrounding quotes at lines 350, 351, 353 and 420 (see decision 1).

Nits

• _data/conferences.yml:95: the location title: PyCon Côte d'Ivoire 2027 still uses the straight apostrophe. It no longer matches conference + year.
• Series follows are keyed on the raw conference string (static/js/action-bar.js:82-86, conference-manager.js:46). Anyone who already followed the straight-apostrophe spelling will no longer match. Page slugs are unaffected, because both apostrophes collapse to -.

Tests. No test covers the request's invariant: a conference page must render valid JS for names or places that contain an apostrophe. There is no fix test to run against the base.

• Data (REVIEW.md): uv run --python 3.11 … python utils/sort_yaml.py --skip_links exited 0: ✅ 1243 conferences passed validation, 🎉 Conference data sorting and cleaning completed successfully. git diff --stat -- _data printed nothing, so there is no post-merge rewrite.
• npm ci exited 0. npm test: Test Suites: 15 passed, 15 total / Tests: 423 passed, 423 total.
• No Python changed, so I did not run ruff or pytest.

Bounds. I got the change from the API diff and checked out refs/pull/512/head. rev-parse matched 843c3e9. I read in full: the diff, the entry, REVIEW.md, AGENTS.md, _layouts/conference.html script lines 345–425, and the _config.yml page_gen block. I skimmed: _includes/head.html (uses jsonify, fine) and the slug uses in _includes/_layouts. I could not run a Jekyll build in the sandbox. A subagent confirmed the Important finding with node --check on the substituted lines, not on a rendered page. Pre-existing: _layouts/conference.html:350-353,420 interpolate data into single-quoted JS strings without escaping, so any future entry with a ' in conference or place breaks its page the same way.

---

Generated by Claude Code