Repository navigation
Publish an Activity RSS feed at /activity/feed.xml #280
Description
Follows the Activity RSS feed decision in #266. Related to #271, but not one of its work items.
Why. Decided in #266: a second feed for Activity. It gives one subscription covering every library release and lecture update, which GitHub's per-repository release feeds don't. /feed.xml stays News-only.
Work.
- The feed page. Add
pages/activity-feed.xml(layout: null,permalink: /activity/feed.xml,sitemap: false), built from Compute the Activity rows at build time, with tests #276's rows:- the latest 50 items, in RSS 2.0 to match
/feed.xml; - each item's
guidbuilt from date, type and project, since lecture URLs repeat; - each item links to its day on
/activity/.
- the latest 50 items, in RSS 2.0 to match
- Discovery. Add
<link rel="alternate" type="application/rss+xml">for both feeds in_layouts/default.html. - Links. If the rail has shipped, turn on its "Activity feed" link. Otherwise the rail adds it when it ships.
Acceptance criteria
-
/activity/feed.xmlvalidates with the W3C feed validator. - Its newest item matches the top of
/activity/. -
/feed.xmlis unchanged. - Both feeds are advertised in
<head>.
Activity
mmcky commentedon Sep 29, 2026
Feed rules (decided 2026-09-29). These are hard to change once people subscribe.
tag:URI withisPermaLink="false". It must not change once published.bookrows read "Book update: …".date_to_rfc822: the site runs on Sydney time, so it would shift every entry back a day.mmcky commentedon Sep 30, 2026
Unblocked (2026-10-01). The replayed days are published: #293 added the feed's first lecture entry (2026-09-29), so launching the feed won't announce the paused days as a burst of new items. The rail is live (#291), so the PR for this issue adds the rail's "Activity feed" link (
bi-rss) after "View all activity", as #291's notes say.One thing to settle when planning: the June to September backfill (QuantEcon/reports-activity#91) will later add older rows. Feed readers would show them as new, unread items. Either launch after the backfill, or accept that.