docs/THE ROKU CHANNEL/video-on-demand/index.md:12 references doc:live-feed-specifications in the Specifications section, paired with the Roku-Hosted (Ingest) Specs entry:
- Roku-Hosted (Ingest) Specs
- Partner-Hosted (Feed) Specs
The slug doesn't resolve in this repo. A reader on the VOD landing page sees one working link to ingest specs and one broken link to feed specs.
Recommendation: add a feed-spec reference page for partner-hosted VOD content.
The Specifications section reads as a deliberate two-option choice: partners pick Roku-Hosted (push content to Roku via the ingest pipeline documented in delivery) or Partner-Hosted (host content yourself and provide a feed Roku consumes). The ingest path is fully documented; the feed path has no v2 page, leaving partners without guidance on the second option.
Closest existing pages don't fill the gap:
content-feed, search-feed, ovp-linear-ingest-spec cover different VOD/linear concerns- The
delivery page is specifically Roku-Hosted ingest
docs/THE ROKU CHANNEL/video-on-demand/index.md:12 references
doc:live-feed-specificationsin the Specifications section, paired with the Roku-Hosted (Ingest) Specs entry:The slug doesn't resolve in this repo. A reader on the VOD landing page sees one working link to ingest specs and one broken link to feed specs.
Recommendation: add a feed-spec reference page for partner-hosted VOD content.
The Specifications section reads as a deliberate two-option choice: partners pick Roku-Hosted (push content to Roku via the ingest pipeline documented in delivery) or Partner-Hosted (host content yourself and provide a feed Roku consumes). The ingest path is fully documented; the feed path has no v2 page, leaving partners without guidance on the second option.
Closest existing pages don't fill the gap:
content-feed,search-feed,ovp-linear-ingest-speccover different VOD/linear concernsdeliverypage is specifically Roku-Hosted ingest