Examples

Official release feed for one repository. Use this pattern when a project publishes product or infrastructure updates through GitHub releases.

GitHub-hosted discussion stream rather than a release feed. Use this when the important signal lives in community or maintainer discussions.

Operational status feed with volume limits to keep the stream focused. Use this for incidents, maintenance notices, and service health updates.

Straightforward publisher-managed blog feed. Use this when one company or project blog is the source of truth for updates.

Newsletter-style RSS feed from a Substack publication. Use this when long-form updates are published through an email-first platform.

Medium publication feed. Use this when a project publishes through Medium rather than its own blog or newsletter stack.

Topic-search RSS feed aggregated by Google News. Use this when you want broad news coverage around a topic, company, or phrase rather than updates from a single publisher.

URL format: Use when:7d for the last 7 days. Wrap exact phrases in %22...%22. Change hl/gl/ceid for locale.

Standing search-query RSS feed rather than a single publisher feed. Use this when the source definition is a topic query across a larger network.

Query syntax: Use OR between terms. points=N filters by minimum score. count=N limits results per poll.

Subject-area research feed instead of a site section feed. Use this when the stream you want is organized by academic category or discipline.

Community forum stream rather than a publisher-managed blog. Use this when discussion threads themselves are the thing you want to monitor.

Self-linking card grid where each listing item is already the canonical article link. Use this when the listing page exposes enough metadata to avoid heavier page-level extraction.

JavaScript-rendered listing that needs an explicit wait and keeps page-level fallback selectors. Use this when cards load late or article pages carry more reliable metadata than the index.

Page selectors: pageTitleSelector and pageDateSelector extract metadata from each linked article page, not the listing. Use these when the listing cards lack reliable dates.

Single-account timeline with retweets excluded. Use this when one official account carries most of the signal and reposts would add noise.

Maintained list of related accounts with reply filtering. Use this when the signal comes from a known group rather than one account or one keyword query.

Standing topic query with boolean terms, exclusions, and an engagement threshold. Use this when the query logic itself defines the source better than any fixed account list.

Query operators: Use OR between terms, parentheses for grouping, -is:retweet / -is:reply to exclude, has:links for link-bearing posts, min_faves:N for engagement threshold.

Sort order: recency uses incremental cursor-based polling. relevancy re-ranks on each poll and may return duplicates.

Authenticated API polling against a top-level array response. Use this when the upstream already exposes the exact item collection you want as one list endpoint.

JSONPath: $[*] selects every element in a top-level array. Use $.items[*] when items are nested under a key.

Authenticated API polling against a nested search-results payload. Use this when the source is defined by query logic rather than a fixed collection endpoint.

JSONPath: $.items[*] selects each element inside a nested "items" array. Match this to the actual response shape.