Add Channels page (no-code + API)#179
Draft
moskovich wants to merge 3 commits into
Draft
Conversation
Deploying docs with
|
| Latest commit: |
ab8e554
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://dcbf1048.docs-dhu.pages.dev |
| Branch Preview URL: | https://docs-channels.docs-dhu.pages.dev |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds a Channels page to fill a real gap: the docs cover playlists (ff-cli, Hosted Feed) but never explained how to make a channel — even though we're now pointing partners (NEORT, OCCUPY) at self-serve channel creation. Adds it to the nav after Hosted Feed.
The page covers:
feed.feralfile.com/api/v1/channels).Grounding
The API path is verified against the dp1-feed-v2 OpenAPI (channel endpoints + Bearer auth) and the channel extension schema. ff-cli has no channel command, so the page doesn't imply one.
The no-code (web) tab describes publisher.feralfile.com at a conceptual level — I wrote it without access to the actual UI screens. Please confirm the flow wording (sign in → create channel → add playlists → publish/sign) matches what the publisher actually does, and correct any step names. Opened as a draft for that reason.