status: active
timestamp: 2026-06-20
tags: [feeds, rss, atom, json-feed, syndication, seo]
Three-format feed publishing — RSS 2.0 + Atom 1.0 + JSON Feed
Every content site publishes RSS, Atom, JSON feeds 2.0, source-of-truth for oriz-omnipost), /atom.xml (Atom 1.0), /feed.json (JSON Feed v1.1). oriz-kit ships <FeedDiscovery /> + generators.'
Three-format feed publishing — RSS 2.0 + Atom 1.0 + JSON Feed
Decision
Every content-bearing site in the family publishes three feed formats at fixed paths:
| Path | Format | Spec | Service file |
|---|---|---|---|
/rss.xml | RSS 2.0 | RSS Advisory Board | (Astro built-in / oriz-kit helper) |
/atom.xml | Atom 1.0 | RFC 4287 | services/monitoring/monitoring/seo/atom-feed.md |
/feed.json | JSON Feed v1.1 | jsonfeed.org | services/monitoring/monitoring/seo/json-feed.md |
RSS 2.0 stays the source-of-truth for
oriz-omnipost cross-posting (locked
in cross-post-engine.md); Atom + JSON
Feed are for human readers / modern feed-tooling that prefers those
formats.
Why
Different feed readers / crawl pipelines auto-discover different formats. Publishing only one loses subscribers using a reader that can’t auto-discover it. Concretely:
- RSS 2.0 has the largest install base (Feedly, Inoreader, legacy readers, every podcast app), so it stays the canonical source.
- Atom 1.0 is preferred by some older newsreaders + a few search-engine crawl pipelines that expect strict, namespaced XML with required IDs and timestamps.
- JSON Feed v1.1 is preferred by modern dev-friendly readers (NetNewsWire, Feedbin, custom tooling that wants plain JSON instead of an XML parser).
Cost to publish all three: one build-step helper per format. There is no runtime service, no quota, no card — they are static files served by Cloudflare Pages.
Implementation
@chirag127/oriz-kit ships:
<FeedDiscovery />component — injects all three<link rel="alternate">tags into<head>:<link rel="alternate" type="application/rss+xml" href="/rss.xml" /><link rel="alternate" type="application/atom+xml" href="/atom.xml" /><link rel="alternate" type="application/feed+json" href="/feed.json" />
generateRssFeed(posts),generateAtomFeed(posts),generateJsonFeed(posts)helpers — each consumes the samePost[]shape, emits valid output.- A single Astro integration that wires all three into
dist/atastro buildtime on every site.
Implications
- Every site repo’s build step writes
dist/rss.xml,dist/atom.xml,dist/feed.json. <FeedDiscovery />lands in the layout component every site inherits from oriz-kit — no per-site wiring.oriz-omnipostcontinues to read/rss.xmlas the canonical feed for cross-posting; Atom + JSON Feed do NOT need omnipost adapters (they are for direct subscribers, not for fan-out).- IndexNow ping (
services/monitoring/monitoring/seo/indexnow.md) fires once per published canonical URL — independent of feed format. - If a feed format spec evolves (Atom moves to a successor, JSON Feed v2), swap the generator helper in oriz-kit; every site picks it up via dependency bump.
- Per-extension changelogs (subdomains under
oriz.in) follow the same three-format rule — readers should be able to subscribe to any extension’s release stream in their preferred format.
Cross-refs
- Atom 1.0 feed service
- JSON Feed service
- SEO services index
- Cross-post engine — RSS 2.0 is its source-of-truth
- SEO three pillars — discovery / instant-indexing / semantic-markup; feeds ride alongside
-
— `
` + generators live here - No card-on-file rule