ADS-112 Document Ads channels#744
Conversation
Co-Authored-By: maarten.rimaux <maarten.rimaux@dolby.com>
Co-Authored-By: maarten.rimaux <maarten.rimaux@dolby.com>
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
|
| customProps: { | ||
| icon: '📚', | ||
| }, | ||
| items: ['concepts/channels'], |
There was a problem hiding this comment.
@MaartenRimaux If you use an auto-generated sidebar, you don't have to stack all of these PRs on top of each other. 😉
| items: ['concepts/channels'], | |
| items: [{ type: 'autogenerated', dirName: 'concepts' }], |
There was a problem hiding this comment.
Good suggestion — an autogenerated concepts sidebar (ordered via sidebar_position frontmatter) would remove the per-PR sidebarsAds.ts edits and naturally keep "Getting started" first. Since this changes the sidebar structure the epic owner approved for the stacked PRs, I've asked @MaartenRimaux to confirm before switching all of them over.
| { | ||
| type: 'category', | ||
| label: 'Getting started', | ||
| description: 'Set up your first stream with OptiView Ads!', | ||
| collapsed: false, | ||
| customProps: { | ||
| icon: '🚀', | ||
| }, | ||
| link: { type: 'doc', id: 'getting-started/index' }, | ||
| items: [{ type: 'autogenerated', dirName: 'getting-started' }], | ||
| }, |
There was a problem hiding this comment.
Uhhh shouldn't "Getting started" still be the first category? 🤔
There was a problem hiding this comment.
Agreed — "Getting started" should stay first. I inserted "Core concepts" above it by mistake; I'll move it below "Getting started". (Tracking the exact sidebar structure together with the autogenerated-sidebar suggestion in the sibling thread.)
2 participants
Summary
Add the canonical V2 Channels concept and API guide on top of the ADS-110 versioning foundation while leaving frozen V1 content unchanged.
The guide connects channel identity and configuration to origins, breaks, events, templates, marker detection, and integrations; explains wallclock versus PTS scheduling; and documents Dashboard navigation plus equivalent Basic-authenticated CRUD/list/detection examples.
It also records pagination/filter/sort constraints, organization-scoped
customAssetKeyuniqueness, service-side timing fallbacks, read-onlydetectionEnabled, and dedicated detection enable/disable endpoints.Link to Devin session: https://dolby.devinenterprise.com/sessions/b934d3445fec4fd8aa7c8dbdcedfb3bc
Requested by: @MaartenRimaux