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.
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.
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.