ADS-631 Ads: how-to guide to serve the Break Manifest from your CDN

[MaartenRimaux]

Summary

Jira: ADS-631

New how-to guide: Serve the Break Manifest from your CDN. It shows how customers can serve the Break Manifest from their own domain, next to their stream, by forwarding a path on their CDN to OptiView Ads.

File	Change
ads/how-to-guides/serve-break-manifest-from-your-cdn.mdx	New guide: how it works, 4 setup steps, verify, troubleshooting
ads/assets/img/break-manifest/served-from-your-cdn.svg	Diagram with example domains, same style as side-loading.svg
ads/how-to-guides/index.mdx	Intro now mentions the new guide
ads/concepts/break-manifest.mdx	New entry in Related resources

Decision log

• Vendor-neutral only: no CloudFront/Fastly/Akamai recipes.
• Whole OptiView Ads path forwarded: everything from /manifest/v1 onwards is forwarded unchanged.
  • The CDN rule stays simple, and future endpoint versions need no CDN change.
  • Recommended URL, next to each stream: example.com/channel-5/manifest/v1/ORG-ID/channels/CHANNEL-ID.
  • Simpler alternative: one /manifest/ path for all channels on the same domain, with no rewrite.
• Regions: US examples with the standard Regional domains note, plus a US/EU domain table in "Before you start".
• Placeholders: ORG-ID / CHANNEL-ID, the same as the SDK and player integration pages.
• Channels endpoint only: the /routes/ endpoint is feature-flagged and not publicly documented yet.
• Requirements checked against the code:
  • X-Manifest-Signature: all three SDK cores reject a manifest without it or with a bad one.
  • Cache-Control = active polling interval.
  • CORS * with the signature header exposed.

Test plan

• npm run build passes (no broken links)
• Prettier + spellcheck (mdxlint) pass on changed files
• SVG checked visually
• Review the rendered page in the preview

Generated with Devin