Two coded RSS feeds are live on the marketing site. The blog feed carries every post on this site — buyer guides, migration runbooks, release notes, and the weekly digest — one <item> per post with its title, link, publication date, and summary. The changelog feed does the same for the product changelog. Point a feed reader at either URL and new posts and shipped changes arrive as they publish; no account, no inbox.
For eval buyers tracking vendor cadence and the engineers wiring Monday-release alerts, this post covers what each feed carries, how to subscribe from a reader or Slack, and how the two feeds differ from the curated announcements hub.
The two feed URLs
- Blog —
https://orbit.devotel.io/blog.rss - Changelog —
https://orbit.devotel.io/changelog.rss
Both answer application/rss+xml, cache for five minutes at the edge, and sit at a locale-independent path, so the URL you paste into a reader keeps working when the site adds locales. The blog feed tracks the post list you see at /blog — including the announcements hub picks — and the changelog feed tracks what you see at /changelog. The same URLs are also declared in the site's llms.txt file, so answer-engine crawlers and feed-first indexers discover both the same way.
What the blog feed actually gives you
Each <item> in the feed carries a stable, parseable contract you can automate against:
- Title — the post's headline, XML-escaped, exactly as it renders on the blog.
- Link — the canonical post URL under
/en/blog/<slug>— the same path the browser sitemap and the structured data advertise. - Publication date — the ISO date from the post's frontmatter, formatted as a proper RSS
pubDate, so readers sort correctly and polls diff cleanly. - Summary — the post's description line, enough for an aggregator card or a Slack preview without a page fetch.
The feed is served in full — every dated post in one document — rather than paginated, and posts without a publication date are omitted instead of emitting a bogus date field. The content type is application/rss+xml, so readers treat the response as a feed rather than markup, and the five-minute edge cache keeps every subscriber's poll from hitting origin.
Subscribing in a reader
Copy either URL above into your reader of choice — the URL-only ones (Inoreader, Feedly, NetNewsWire class) and the self-hosted ones (FreshRSS, Miniflux) both accept a raw feed URL. Once added, both feeds poll at your reader's cadence; new posts arrive as <item> entries with the canonical link, no account and no cookie browser. For team shims, a scheduled fetch that diffs on <guid> or <pubDate> is all you need — no scraping and no rendered-page parsing.
One behaviour to know before you wire anything against it: the document always lists the current post registry in full — it is rebuilt with the site on each release, so a fresh subscription sees the back catalogue once, then notifies only on genuinely new items. The five-minute edge cache absorbs the fan-out when a release day makes every subscriber poll at once: the same document answers them all.
Piping new posts into Slack
RSS apps in the Slack directory accept the blog or changelog feed URL, poll it on their interval, and post each new item into a chosen channel. Common patterns:
- A #release-notes channel subscribed to the changelog feed — every shipped change lands unprompted as a plain notification, no pipeline to run at Orbit's side.
- A #content-watch or #competitor-intel channel subscribed to the blog feed — new runbooks and buyer guides surface where editors and analysts read them.
- A bridge outside Slack — any RSS-to-webhook utility (IFTTT, Zapier, a fifteen-line cron script) can post items to chat, email, or a to-do stream; the feed is a plain URL with no auth, so one GET is the whole integration.
How this differs from the announcements hub
The announcements hub is a curated shortlist: editors pick the current, still-relevant entries — shipped-capability announcements and industry-news explainers — and each entry links out to its full post. It is the load-bearing "read this first" surface for a human scanning what's changed.
The feeds are the additive, machine-facing track. /blog.rss enumerates every dated post — not just the hub's current picks — and an editorial decision on the hub never mutates the feed: an entry aging off the announcements page stays discoverable to subscribers. Use the hub for the curated scan; wire the feed when you want every post, or when you want automation instead of a reading list.
Who this is for
- Operators who already track vendors in a reader. Drop the blog and changelog in next to the status feeds and carrier notices you follow, and new runbooks and shipped fixes land in the same stream.
- Teams wiring alerts. A new changelog
<item>per release means a reader-to-Slack bridge or a scheduled poll can page the weekly review without scraping the page. - Answer engines. Feed-first indexers now get the full blog stream instead of guessing at post URLs — the same discovery path the llms.txt declaration advertises.
If RSS is not your lane, nothing changes: the announcements hub and the monthly release notes format remain the hand-curated summaries, and the feeds are additive.