Repoint all wxyc.info links to the new wxyc.org successor pages

[jakebromberg]

Problem

Every listener-facing link from wxyc.org into wxyc.info becomes a dead link at the 2026-08-31 cutover (WXYC/wiki#93). Full inventory, verified against origin/main @ a148ac2 on 2026-08-08:

File	Line	Target
components/Header.js	107	http://www.wxyc.info/playlists/recent
components/DropdownMenu.js	49	http://www.wxyc.info/playlists/recent
content/page/programming.mdx	54	http://wxyc.info/playlists/radioWeek
content/page/programming.mdx	56	http://wxyc.info/playlists/searchPlaylists
pages/playlist.js	35, 42	both, inside the commented-out prototype

This is the last step of Phase 4's D3 work: the three successor pages must exist first, then the nav points at them, then wxyc.info can go dark.

Desired end state

No wxyc.info link remains anywhere in website. Header, dropdown, and the programming page point at the three new local pages. A listener who used to reach the live playlist, the show archives, or airplay search from wxyc.org still reaches an equivalent page.

Where

The five sites in the table above. Whatever paths the three page tickets actually landed are the targets — read them off main, do not assume the suggested filenames.

Constraints

• All three successor pages must be merged before this lands, or the nav points at 404s. That is the blocking relationship, and it is the whole reason this is a separate ticket.
• content/page/programming.mdx is TinaCMS-managed content. Editing the file in the repo is correct here, but check whether TinaCMS will treat it as a conflict on next CMS edit; note anything surprising in the PR body.
• Links become relative internal links (/playlist, …) — use next/link where the surrounding code does, not bare <a href> to an absolute URL.
• website#93 ("Reconfigure top site nav", opened 2025-07-13) proposes a broader nav restructure and contains a "Recently Played" entry still pointing at wxyc.info. It predates the turndown and is not this ticket. Do not implement its full restructure here; do reference it, and flag in the PR body whether it should be closed as superseded — that call belongs to a human.
• Deploying main publishes to the live public site.

Acceptance criteria

• grep -rn "wxyc\.info" --include="*.js" --include="*.jsx" --include="*.mdx" . (excluding node_modules) returns zero hits.
• Header and dropdown link to the live-playlist page; programming.mdx links to the archive and airplay-search pages.
• Internal links use the site's existing routing idiom.
• Every new link resolves to a page that exists on main.
• npm run lint and npm run test green. (npm run check-format fails on 19 files already dirty on main — leave them.)

Related

• Parent: WXYC/wiki#91 (Phase 4). Milestone: WXYC/wiki#93, deadline 2026-08-31.
• Blocked by all three website page tickets.
• See also website#93.

Blocked by

• feat: public live-playlist page (wxyc.info /playlists/recent successor) #211 — live-playlist page
• feat: public airplay-search page (wxyc.info /playlists/searchPlaylists successor) #212 — airplay-search page
• feat: public historical-archive page (wxyc.info /playlists/radioWeek successor) #213 — historical-archive page — MERGED 2026-08-10 as pages/playlists/archive.jsx. Its target path is therefore settled: content/page/programming.mdx:54 points at /playlists/archive.

All same-repo; each must be merged before the nav can point at it. Both remaining blockers became startable 2026-08-10, when their shared upstream WXYC/Backend-Service#2061 was confirmed deployed (PUBLIC_READ_ORIGINS set; api.wxyc.org returns Access-Control-Allow-Origin: https://wxyc.org).

Note on the grep acceptance criterion. As of origin/main it returns six hits, not the five inventoried above: the sixth is pages/playlists/archive.jsx:23, a docblock reading "the successor to wxyc.info/playlists/radioWeek, which dies at the 2026-08-31 tubafrenzy cutover." That is accurate provenance prose and should not be deleted to satisfy a grep — narrow the AC to link sites (href= / markdown links) or exempt comments explicitly.

[jakebromberg]

Status update: one of three blockers cleared; the other two are now startable (2026-08-10)

#213 closed 2026-08-10 — the historical-archive page shipped as pages/playlists/archive.jsx. So this ticket's ## Blocked by list is down to website#211 and website#212, both of which became startable today: their shared blocker WXYC/Backend-Service#2061 is merged and deployed, with PUBLIC_READ_ORIGINS set on the prod backend. Verified live — api.wxyc.org now returns Access-Control-Allow-Origin: https://wxyc.org on GET /flowsheet, GET /flowsheet/search, and GET /flowsheet/range.

Two notes for whoever picks this up:

The path for the archive link is now known, not suggested. This ticket says "whatever paths the three page tickets actually landed are the targets — read them off main, do not assume the suggested filenames." One of them is settled: content/page/programming.mdx:54 should point at /playlists/archive, not the suggested filename. The other two are still open.

The grep AC has a sixth site, and it is not a link. The AC is grep -rn "wxyc\.info" --include="*.js" --include="*.jsx" --include="*.mdx" returning zero. As of origin/main today that returns six hits, not the five in the inventory table: the five listed, plus pages/playlists/archive.jsx:23, which is a docblock reading "the successor to wxyc.info/playlists/radioWeek, which dies at the 2026-08-31 tubafrenzy cutover." That is accurate provenance prose and deleting it to satisfy a grep would be a loss. Either narrow the AC to link sites (href=/markdown links) or explicitly exempt comments — otherwise the AC and the codebase disagree the moment it is checked.

Full triage context: WXYC/wiki#109.

[jakebromberg]

PR opened: #222.

Both remaining blockers cleared on 2026-08-11 (#211 and #212), so all three successor pages are on main and live in prod — verified 200 on https://wxyc.org/playlist, /airplay-search, and /playlists/archive before repointing.

Two things worth recording against this ticket's body:

One target differs from the inventory's assumption. This ticket says to read the landed paths off main rather than assume the suggested filenames — correctly, as it turns out. /playlists/archive matched, but the airplay-search page landed at /airplay-search (top level, pages/airplay-search.jsx), not under /playlists/. The live playlist landed at /playlist (pages/playlist.jsx).

The fifth inventoried site is gone. The table lists pages/playlist.js:35,42 — "both, inside the commented-out prototype." That file was rewritten as pages/playlist.jsx by #211, and its only surviving wxyc.info occurrence is a provenance docblock at line 13. So there were four link sites to change, not five.

On the grep acceptance criterion. Implemented as this ticket's comment recommends — narrowed to link targets. The PR adds __tests__/wxycInfoLinks.test.js, which asserts no href or markdown link anywhere in the repo targets wxyc.info, that each of the four sites links to its named successor, and that each successor route resolves to a page that exists. Three prose mentions survive on purpose (docblocks in the three successor pages, plus README.md); each names the page it replaces. Verified red against the pre-change tree on all four sites.

A source-level test rather than a render test for two reasons neither of which a component test can work around: Header.js and DropdownMenu.js hold JSX in .js files, which this repo's vitest transform rejects outright, and the third site is TinaCMS-managed .mdx.

npm run test (287 passed), npm run lint (no errors), and the exact CI build (next build under tinacms dev) are all green locally; the exported site contains zero wxyc.info occurrences.