RSS feeds

distributiondevelopers

Every Drumroll workspace exposes RSS 2.0 feeds at predictable URLs. No setup, no toggle - the moment you publish, the feed updates. Subscribers in any feed reader pick up new content on their next poll.

Feed URLs

Two feeds per workspace:

  • https://<your-slug>.usedrumroll.com/changelog.xml
  • https://<your-slug>.usedrumroll.com/guides.xml

If your workspace slug is acme, those are https://acme.usedrumroll.com/changelog.xml and https://acme.usedrumroll.com/guides.xml.

You don't actually need to share the .xml URLs - the public changelog and guides pages advertise the feed via <link rel="alternate" type="application/rss+xml"> in the document head. Most readers auto-discover the feed when given the regular page URL.

What subscribers can do with it

Read in a feed reader

Paste the URL into Feedly, Inoreader, NetNewsWire, Reeder, or whichever reader your team uses. New entries show up on the next poll, usually within 30 minutes.

Pipe into Zapier / IFTTT / Make

RSS triggers are first-class in every major automation platform. Common workflows:

  • New RSS item → tweet from the company account
  • New RSS item → post to a different Slack channel (e.g. for translations team)
  • New RSS item → create a Notion database row
  • New RSS item → send a custom email via Resend / Postmark

RSS-to-email digest

Mailchimp and ConvertKit both offer "RSS-to-email" campaigns - a templated digest sent on a schedule, populated from your feed. The cheap path to "email subscribers" before Drumroll ships a native one.

Embed on another site

Most static-site generators (Hugo, Astro, Eleventy) can render an external RSS feed as a list. Useful if you want to show recent releases on your marketing homepage without iframing the embed widget.

Feed shape

Standard RSS 2.0 with an Atom self-link. Each item includes:

  • title - the entry/guide title
  • link - canonical URL on your workspace's public surface
  • guid - the entry/guide UUID, stable for dedupe
  • pubDate - the publish timestamp in RFC 822 format
  • description - full rendered HTML body, wrapped in CDATA
  • category elements - one per tag

Caching

Feeds are edge-cached for 10 minutes with stale-while-revalidate. Polling more often than once a minute won't get you fresher data; readers usually poll every 15-60 minutes anyway.

Not yet supported

  • Private / draft entries - feeds only expose published content.
  • Atom 1.0 (RSS 2.0 only; ~every reader consumes both).
  • Per-tag filtered feeds. The workspace-wide feed is the only option for v1.
  • WebSub / PubSubHubbub push notifications (consumers poll).