Hello all!
Thank you for welcoming me at today’s Watercooler Chat [Slides here] where I provided a few key Documentation updates, which I’m also sharing below.
Sharing the latest structured update on the Livepeer Documentation Restructure, aligned with the RFP goals outlined here: RFP — Documentation Restructure - #10 by honestly_rich
Summary - Documentation Requirements
Key points
-
Stakeholder‑focused documentation.
-
AI‑first, LLM‑readable structure.
-
Ecosystem‑integrated resources.
-
Single‑source‑of‑truth documentation
Timeline of Work
To complete this work, the project was structured into 4 main phases*.* These phases move from analysis → stakeholder engagement → rebuild & rewrite → automation and AI.
- [complete] Phase 1: Foundational Audit, IA, Deprecations
- [complete] Phase 2: Stakeholder Alignment & Feedback (NB: stakeholder engagement remains active and welcome)
- [now] Phase 3: IA Implementation, Priority Rewrites, Site Integration
- [next] Phase 4: Automations, AI Features, Processes
Phase 1: 
Audit & Analysis
Completed deliverables
-
Content inventory
-
Pain Point & Solution Map
-
Deprecation/Migration matrix
-
Persona journeys
-
Stakeholder mapping
-
IA framework options & recommendations
-
AI Feature Analysis
Direct findings:
-
Livepeer documentation is heavily fragmented across Studio, Cloud, Network, Orchestrators, Delegators and Gateway docs.
-
Significant duplication between Studio guides and developer guides.
-
Critical onboarding paths lack clarity - especially Gateway onboarding, Orchestrator setup, and differentiating Studio vs Cloud.
-
Developers frequently land in the wrong section due to the slider navigation.
-
Many pages are outdated, referencing deprecated features or dead links.
-
IA does not map to Personas; pathways do not reflect real user journeys.
Core Requirements Identified:
-
Fix outdated, contradictory, fragmented content.
-
Create a persona-led information architecture.
-
Remove duplicate Studio/Cloud/Network docs.
-
Integrate enterprise pathways (Gateways, Daydream, BYOC).
-
Define clear ownership and governance over the docs’ content.
Phase 2: 
Stakeholder Engagement
Completed deliverables
-
Stakeholder and community feedback collected through analysis of forum & discord posts as well as stakeholder feedback via meetings & feedback form
-
Feedback consolidation completed.
-
Watercooler update delivered on 25 November.
-
Persona requirement insights fed into IA.
-
IA drafted for review
NB: Feedback & Engagement remains ongoing throughout the process!
Please reach out if you’d like to contribute, or share your thoughts in this feedback form
Feedback Summary
-
Paths confusing (AI vs Video vs Studio; protocol vs product; network vs app).
-
Key technical info missing (orchestrators, LPT/governance, gateways, protocol docs).
-
Need real, runnable examples + full workflows (AI, BYOC, streaming).
-
Structure inconsistent → want unified API + consistent workflows.
-
Governance unclear → need provenance, ownership, contributor paths.
-
Roles unclear → want simple responsibilities + decision flows.
Selected Feedback Quotes
Recommendations
-
Add Builder / Partner / Project HUBs with easy contribution flows.
-
Streamline homepage with clear entry points and zero→hero onboarding.
-
Automate content updates (Luma, gateways, repos, forum/Discord ingestion).
-
Build unified API surface + cross-linked stack (protocol ↔ gateway ↔ orchestrator ↔ product).
-
Create full orchestrator + gateway guides (job types, pipelines, governance).
-
Add dedicated governance/delegator layer (decision trees, safety, fees).
-
Add AI-first features (AI assistant routing, LLM-ready pages, metadata).
[Now] Phase 3: 
IA Implementation & Rewrites
Active tasks:
-
IA finalisation and styling
-
Rewriting core sections (Home, About, Community, Protocol)
-
Aggregating ecosystem resources & reaching out to key contributors
-
Building Builder Hub, Project Hub, Contacts page, Resources page
-
Migration guides and deprecation workflows identified
-
AI‑first metadata and semantic markup
-
External doc mapping (Gateways, SPEs, Projects)
Tasks still queued:
-
Protocol, Gateway, Orchestrator, Developer technical deep dives
-
Migration tables and before/after guides
-
Error‑path quickstarts (AI + Video)
[Next] Phase 4: 
Automations, Pipelines & AI
Upcoming tasks:
-
Community contribution pipelines
-
External docs auto‑sync (Luma, Gateway resources)
-
Social links automation
-
AI search + AI assistant customisation
-
Multilingual readiness
-
SEO analytics and canonical processes
Thankyou!
Happy to answer questions or walk through the full IA and rewrite the roadmap - and thanks to everyone across the Foundation, Livepeer Inc., Daydream, Streamplace and the broader community who contributed during Phases 1 and 2.
