Skip to content

Support

How SHRD collects content and keeps collections updated.

SHRD helps publishers turn the best of the web into live collections they can edit, publish, embed, and monetize. This page explains the practical workflow.

Collecting content

Content can be saved once or supplied by recurring sources.

Save individual links

Use SHRD to save posts, videos, articles, product pages, clips, and other public URLs into a collection.

Use the browser extension

The extension lets you capture content while browsing. When it can identify a useful source, you can also add that source to the collection.

Attach recurring sources

A collection can follow sources such as manual URL lists, X Lists, managed X handles, YouTube channels, and YouTube playlists.

Start from a template

SHRD can provide reusable source templates that a publisher can adopt, tune, and apply to its own collections.

Keeping collections fresh

Updates are controlled by source trust, policy rules, and exception handling.

The useful version of automation is not a black box. Publishers decide which sources are trusted, which ones create exceptions, and how aggressively SHRD should filter or prune the collection.

  1. 1
    SHRD checks the collection sources on the cadence set for that collection.
  2. 2
    New items are matched against freshness, keyword, source, and content rules.
  3. 3
    Trusted sources can publish automatically when the publisher allows it.
  4. 4
    Lower-confidence or newly calibrated sources create dashboard exceptions before anything goes live.
  5. 5
    Old or low-value items can be pruned by time-based rules so the collection stays useful.

FAQ

Straight answers for publishers and editors.

What is a collection?+

A collection is an editable set of links, posts, videos, embeds, and source-fed items around a topic. It can live on SHRD, be embedded on a publisher site, or be reused through the publisher workflow.

What is a source?+

A source is a place SHRD checks for new content. Sources can be manual URLs, browser-extension saves, X Lists, managed X handle groups, YouTube channels, YouTube playlists, and other supported feeds.

Does every new item publish automatically?+

No. Publishers choose the policy. Trusted sources can publish automatically, while uncertain sources create exceptions in the SHRD dashboard before they appear in a live collection.

How often do collections update?+

Each collection can have its own update cadence. A publisher might use daily checks for evergreen feeds and manual refreshes for breaking or sensitive collections.

Can SHRD filter what gets added?+

Yes. Collections can use include and exclude keywords, freshness windows, content-length limits, source trust, and exception rules to keep the feed focused.

How do old items leave a collection?+

Publishers can prune manually or use time-based expiration rules. The goal is to keep live collections current without forcing editors to rebuild them from scratch.

Where do exceptions show up?+

Open exceptions are centered in the SHRD publisher dashboard. SHRD can surface exception counts, source health, autonomy posture, and collection status where the publisher manages the collection.

Can the same collection be used in more than one place?+

Yes. A collection can be reused across publisher surfaces, embedded in different placements, or adapted from a shared SHRD template with publisher-specific controls.

Can a collection be sponsored?+

Yes. A collection can support sponsored cards, pinned placements, branded topic hubs, full sponsored collections, or video-supported editorial modules depending on the publisher setup.

Does SHRD create new ad inventory?+

Collections can create incremental sponsorship and video inventory through deeper sessions, video placements, and sponsor surfaces. Exact behavior depends on the publisher integration.

What makes a good first collection?+

Start with a category where the audience already has intent: a sport, event, campaign, creator group, product category, or recurring editorial package with a reliable stream of sources.