Skip to content

Feeds

A Feed Display renders empty when its slug is blank, points at a feed on another site, or matches nothing — the public site always filters to published content.

A feed is a saved, named query over one content type — build it once in the Feed Builder, then point any number of Feed Display modules at it by slug instead of re-specifying the query on every page that wants the same list.

What a feed can filter on

A feed always names a content type, and can optionally narrow by status, a search term, locale, parent page, sort order and a result limit — that's the full set the Feed Builder form exposes. The underlying query model can also filter by category or tag and combine conditions into filter groups, but none of that shows up in the form: a feed built through the admin can only ever be as specific as the fields on screen.

How a Feed Display gets its items

The feedDisplay module can't query anything itself — it only renders whatever list of items it's handed. A separate pass walks the page's layout before it renders, finds every Feed Display, resolves the feed slug each one points at, runs that feed's query, and drops the results in. If your host app doesn't wire that pass into its render path, every Feed Display on the site renders empty regardless of what the feeds themselves contain — the shipped Next.js integration wires it, so this only bites a from-scratch host.

Why a Feed Display shows nothing

Worth checking in this order. The Feed Display's own feed-slug field is blank — hydration skips a blank slug outright rather than treating it as "show everything." The slug doesn't resolve on this site — feed lookup is scoped to the site the page belongs to, so a feed built on one site is invisible to a Feed Display on another, even with a matching slug. Or, most simply, no content currently matches the feed's own filters.