Rewrite developer journey page#761
Merged
DeveloperAlly merged 6 commits intolivepeer:docs-v2from Mar 1, 2026
Merged
Conversation
Replace the skeleton table/mermaid page with an actionable developer journey defining three clear paths: Workload Provider, Workload Consumer, and Core Contributor — each with sub-paths, role definitions, and links to existing docs. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Better define workload provider as creating workloads that run on orchestrators - Traditional route: reorder steps (understand BYOC → build container → run gateway → deploy) - Smart contract path: explain direct contract interaction for orchestrator onboarding, remote node control, and payments — with livepeer-ops as the recommended fork - Update mermaid diagram to show sequential BYOC flow Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
BYOC containers can't be pushed to the network automatically — providers need to coordinate with orchestrators to get containers running on their nodes before routing jobs through the gateway. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Link to ad-astra-video/livepeer-app-pipelines in the BYOC build step for example implementations and integrations. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
its-DeFine
force-pushed
the
developer-journey-rewrite
branch
from
72ffaf6 to
62fae03
Compare
Two options for running an orchestrator: - Option A: Full go-livepeer setup (install, register on-chain, process workloads) - Option B: OrchestratorSiphon + go-livepeer split setup (secure keystore management on one box, workload processing on another — avoids missing rewards) Links to go-livepeer repo/docs and Stronk-Tech/OrchestratorSiphon. Core Contributor moves to Path 4. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Remove orchestrator content from developer journey (back to 3 paths) - Add tip linking to orchestrators section from developer journey - Create v2/orchestrators/orchestrator-journey.mdx with two setup options: A) Full go-livepeer (single machine, register on-chain, process workloads) B) Split setup (OrchestratorSiphon for rewards + go-livepeer for workloads) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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
2 participants
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.
Summary
Test plan
/v2/developers/developer-journey🤖 Generated with Claude Code