Documentation Restructure
Nobody has claimed this yet.
- Dominant language
- MDX
- Stars
- 46
- Forks
- 75
- Avg merge
- 16h 54m
- Merged PRs (30d)
- 1
Description
**Goal:**
Restructure, refresh, and modernize Livepeer’s documentation to make it stakeholder-focused, AI-first, and future-proofed.
**Requirements:**
Use the [RFP process](https://forum.livepeer.org/t/rfp-documentation-restructure/3062) to fund a small documentation team to deliver a full documentation overhaul that improves usability, accuracy, and consistency across the ecosystem.
Key focus areas:
* Conduct full documentation audit and create a new information architecture (IA).
* Deliver stakeholder-focused onboarding paths (Developers, Delegators, Orchestrators, Gateway Operators).
* Rewrite and consolidate all core docs with updated APIs, SDKs, and examples.
* Integrate semantic structure and metadata for AI-readiness (LLM parsing, embedded assistant, Mintlify integration).
* Deprecate outdated Studio content and unify changelogs and versioning.
* Implement new design, redirects, and accessibility-compliant documentation site.
* Establish long-term maintenance workflow, contribution guide, and ownership model.
**Tracked By:**
https://github.com/orgs/livepeer/projects/16
---
**Additional Context (optional):**
_Add relevant background, dependencies, or related discussions._
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked RFP and project 16 to understand the proposed documentation team and tracked work. Audit the existing documentation and define the information architecture, stakeholder onboarding paths, content updates, AI metadata, site changes, and maintenance workflow. Done means the documented overhaul is delivered across the ecosystem, including redirects, accessibility, versioning, and ownership guidance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- markdown
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100