RFP — Documentation Restructure

RFP Applications
2

Hello all - submitting my RFP to help make Livepeer’s docs world-class! :fire: Look forward to working with the community here! :fire:

Team/Individual Name: Sidney Lane

Contact Information: sidney.lane.contact@gmail.com

Arbitrum Payment Address: 0x3ef3f79C03A27299636A8d16693e6d54f68264De [USDC on Arbitrum]

Total Funding Amount Requested: $25,000

Executive Summary

This proposal outlines a comprehensive plan to restructure and modernise Livepeer’s documentation in line with the Livepeer Foundation’s RFP, making it “stakeholder-focused, AI-first, and future-proofed”

My approach emphasises clear, concise, and well-structured content (following industry best practices) and directly targets Livepeer’s core personas – developers, delegators, gateway operators, and orchestrators – by providing goal-oriented & relatable tutorials, migration guides, and reference materials for each. I achieve this by using the product myself as well as through community engagement & mitigating against pain points.

Over a 10-week engagement (Sept 29–Dec 5, 2025), I will conduct a full content audit and IA redesign, rewrite key guides (quickstarts, API/SDK references, tutorials), implement the new site with embedded AI-friendly features, and deliver style/contribution guidelines.

My Experience & Background

With a background as a leader in a decentralised Compute & AI startup, 8 years of DevRel experience, and over 4 years in crypto & blockchain, I bring the combined perspective of a technical leader and strategist. I’ve also worked as a developer, a researcher, a project manager and a consultant across IBM, the University of Sydney, and Accenture, and I hold degrees in Mechatronics Engineering & Computer Science.

As former deAI startup leadership, developer and prior DevRel, I bring the combined experience of my developer skills, business understanding and communication expertise to this role. I also bring a clear understanding of the level of technical difficulty & product pain points that can be faced by new product users in decentralised technologies and the ability to ELI5 and provide content that targets new users’ interests and targets business goals.

Contributor Overview & Capabilities

I am applying as an individual contributor. My profile and skills include:

  • Technical leadership: Former leadership at a decentralised AI (deAI) startup, where I led product strategy and technical development while building and supporting a community with multiple actors (compute providers, users, partners & AI developers).

  • Blockchain and decentralised systems: 5 years of experience in crypto, including as a devRel & devX lead with a distributed storage company. I understand the Livepeer ecosystem and related concepts like transcoding, decentralised nodes, and staking/delegation. This directly aligns with the RFP’s requirement for “1+ years experience with [the] Livepeer ecosystem” and “streaming/transcoding basics (FFmpeg, GPU workloads)”

  • Technical expertise: I hold degrees in Mechatronics and Computer Science, giving me solid foundations in hardware (e.g. GPUs, video encoding) and software. This technical literacy enables me to accurately document low-level processes (like Livepeer Broadcaster setup or GPU transcoding) and high-level architecture (orchestrators, gateways, on-chain components).

  • Documentation & IA skills: I have led multiple documentation projects using static-site tooling (Docusaurus/Mintlify, GitHub Pages) and established clear information architectures. My skills align with the RFP’s “developer documentation strategy, Information Architecture design, [and] technical writing” requirements. I also understand SEO, accessibility (WCAG), and multilingual workflows, ensuring the final site is discoverable and inclusive.

  • Open-source and community focus: I am experienced with GitHub-based contribution models and community collaboration. As the RFP seeks a “community-first, collaborative, pragmatic” attitude, I will engage core stakeholders (Livepeer Foundation, Livepeer Inc., Streamplace, SPEs) throughout the process and will distil technical complexity into user-focused documentation. I’ll also provide progressive community workflows for a builder’s funnel journey, and can integrate automated escalations, aggregation of questions & AI features & capabilities.

Proposed Approach & Philosophy

To improve Livepeer’s documentation, I will follow a user-centric, AI-enabled, and systematic approach:

  • Stakeholder-focused content audit: First, I will identify the core personas (developers, delegators, orchestrators, gateway operators) and map their journeys. I will also define business & product targets in order to capture multiple KPIs within the docs (eg, Join the community, contact, encouragement to contribute). I will also aggregate common questions from the forum, GitHub and Discord for inclusion gaps. This will also help me to define a tone and culture for the docs (should there be gifs & fun names, etc., for example). I will inventory all existing docs (Livepeer docs, Studio guides, etc.) and assess each page for relevance, accuracy, and stakeholder fit. This audit will reveal outdated or redundant content and highlight gaps.

  • New Information Architecture (IA): Following the audit & information gathering process, I can then propose a new format for documentation that will target user journeys more effectively and promote community engagement while minimising pain points. Using insights from the audit, I will design a clear, hierarchical IA. This may involve restructuring the sidebar, taxonomy, and breadcrumbs to create distinct sections for each user type. Each major section (e.g. Developers, Delegators, Orchestrators, Gateways) will present goal-oriented entry points (“how to start as a delegator”, “setting up an orchestrator node”, etc.). I will apply the Diátaxis framework, providing tutorials (step-by-step guides), how-to and task-based guides (for common operations), conceptual explanations (network architecture, key concepts), and reference (detailed SDK/API docs) with help from the current team and engineers to fill gaps where needed. This ensures the content is easy to scan and lets readers find what they need quickly. Clear headings, bullet lists, and indexed tables of contents will make each page accessible and AI-readable, and SEO considerations can also be optimised.

  • Writing for clarity and AI: I will rewrite all content in plain, concise language to improve clarity, as well as target an uplifting and fun vibe for users (without compromising integrity or burdening the journey). Each document will start with the most important information, and any jargon will be defined or simplified, as recommended by best practices. Importantly, I will embed metadata and semantic structure to be “AI-first, with an embedded natural language search/assistant”. This means using descriptive headings and machine-readable examples (OpenAPI specs, JSON snippets) so that Livepeer’s Mintlify/Docusaurus site can support vector search or chatbot integration. In practice, the documentation will include explicit summaries and keywords for each section, enabling LLMs to retrieve and explain content to users easily.

  • Targeted Guides and Tutorials: I will produce tailored content for each persona. For developers, this includes quickstarts for both AI Jobs and Transcoding Jobs (e.g. “Build your first AI-powered Livepeer app”), full SDK/API references (including new gateway products like Streamplace and Daydream), and code examples. For orchestrators, I will create a streamlined node setup guide with links to Discord support. Delegator docs will feature simple delegation walkthroughs, perhaps incorporating short video demos or diagrams if time permits. Gateway operators (Streamplace, etc.) will have their own section with step-by-step integration guides. Migration guides will help Studio users transition to the new system. In all cases, I will organise content by use case (goal-based tutorials) as the RFP specifies. We will target more than new developers by providing level-up guides where possible and giving ideas on usage - not just technical descriptions - perhaps highlighting community & partner projects.

  • Implementation and SEO: After drafting content, I will implement the revised IA and pages in the chosen docs stack (Mintlify/Docusaurus). I will set up 301 redirects from old URLs to new ones to ensure a single source of truth and avoid broken links. Deprecated pages can be versioned in case of need. AI-first SEO best practices (meta tags, descriptive URLs, sitemap) and accessibility considerations (WCAG) can be applied throughout. Multilingual readiness can also be configured, and basic analytics (to track engagement) will be integrated. AI features and flows can also be added where time permits.

  • Governance and Style: To ensure long-term maintainability, I will develop a documentation style guide (tone, terminology, formatting) and a contribution model. This will align with the RFP’s vision of a unified voice and clear PR workflow. I can also integrate automated triggering processes for approvals into this flow ie github → discord messages. I will hand over a clear process for reporting issues and updating content (e.g. a GitHub issue template or Discord channel for docs feedback).

Throughout, I will work closely with Livepeer’s teams, conducting reviews and RFCs (as per milestones) to gather feedback. This collaborative, iterative method matches the “community-first, collaborative” attitude highlighted by the Foundation and will lead to a user-focused outcome.

Milestones & Timeline

I’ve separated the milestones into essentials, desired and stretch goals to accommodate any flexibility needed with timing, given a tight timeframe for delivery. KPIs can be set accordingly.

Phase 1 – Foundation (Weeks 1–3)

Lay the groundwork: audit, tone, and architecture.

Essential:

  • Full content audit (Livepeer docs, Studio guides, forum, GitHub, Discord).

  • Persona & journey mapping (developers, delegators, orchestrators, gateway operators).
    Draft tone & culture guidelines (voice, fun vs formal balance, engagement hooks).

  • Initial Information Architecture (IA) proposal.

Desired:

  • Early KPI mapping (community join, contribution prompts, contact flows).
    Aggregation of common Q&A from community sources for gap-filling.

Stretch:

  • Draft initial “content matrix” mapping every doc to persona, goal, and KPI.

  • Mockups of possible UI/UX (sidebar/navigation layouts).

Phase 2 – Alignment & Review (Weeks 4–5)

Validate structure, test tone, and begin high-priority rewrites.

Essential:

  • Refine IA after Livepeer team + community feedback.

  • Rewrites for top-priority docs:

    • Developer quickstarts (AI Jobs, Transcoding Jobs).

    • Orchestrator setup.

    • Delegator staking walkthrough.

Desired:

  • Draft migration guide (Studio → new APIs).

  • Tone experiments (gifs, diagrams, fun naming) applied to early docs.

Stretch:

  • Run community RFC on tone & layout prototypes.

  • Create first visuals (flowcharts, system overview diagrams).

Phase 3 – Build & Expand (Weeks 6–8)

Deliver breadth: cover all personas, implement IA live, and expand tutorials.

Essential:

  • Implement new IA in Mintlify/Docusaurus.

  • Expand rewrites: Gateway operators, SDK/API/CLI references.
    Ensure metadata/semantic structure for AI-first search.

Desired:

  • Add level-up tutorials (beyond basics).

  • Highlight community/partner projects as inspiration.

  • Initial SEO & accessibility pass.

Stretch:

  • Add embedded video snippets or interactive demos.

  • Prepare multilingual scaffolding (no translations yet).

Phase 4 – Finalise & Future-Proof (Weeks 9–10)

Polish, hand over, and ensure sustainability.

Essential:

  • Final docs package live with redirects, SEO, and accessibility fixes.

  • Documentation style guide (voice, terminology, formatting).

  • Contribution workflow (GitHub → Discord triggers, PR templates).

Desired:

  • Analytics setup to monitor usage (page views, search queries, drop-offs).

  • Maintenance playbook for ongoing updates.

Stretch:

  • Advanced tutorials (use-case guides, “Build your first app in 10 minutes”).

  • Glossary of key terms for new community members.

Deliverables

By project completion, I will deliver:

  • Content Audit Report: A spreadsheet or visual map of existing documentation, showing status (keep, rewrite, archive) for every topic, organised by persona.

  • Information Architecture Outline: A new site map and sidebar structure, with taxonomic categorisation of content (by stakeholder type and task).

  • Rewritten Documentation: High-quality pages covering:

    • Tutorials and quickstarts for AI and transcoding jobs (for developers).

    • Delegator guides (including new video tutorials or diagrams) to simplify staking.

    • Orchestrator onboarding (node setup, funding, monitoring).

    • Gateway operator guides for integration with Livepeer Cloud SPEs.

    • Migration instructions for migrating from Studio to the core Livepeer APIs.

    • Complete API/SDK/CLI reference material (including real-time and BYOC APIs).
      Any necessary diagrams or visual assets (network architecture, workflow charts) to aid understanding.

  • Fully Deployed Docs Site: A Mintlify/Docusaurus-based documentation portal with all new content, integrated into the Livepeer website. This site will have semantic markup, an embedded natural-language search/assistant feature, and a consolidated changelog/version history.

  • Redirects & SEO/Analytics Setup: Configured 301 redirects for legacy URLs, optimised metadata for search, and basic analytics reporting on documentation usage.

  • Style Guide & Contribution Process: A documented voice and style guide (terminology, formatting, accessibility guidelines) and a clear contribution/PR workflow (templates and processes) for future updates, fulfilling the “Public Workflow” milestone

  • Recommendations for future work: I’ll detail any recommendations or thoughts for future work that could deliver even more value to Livepeer & its ecosystem.

Budget & Pricing

My budget is based on 25 hours of work per week over a 10-week period. All essential needs will be delivered within this timeframe, and desired outcomes should also be possible. Stretch goals can be attempted where time permits.

Conclusion

With a strategic, user-focused approach and the technical background to understand Livepeer’s ecosystem, I am confident in delivering documentation that meets and exceeds the RFP’s goals. My plan follows best practices (clear writing, structured content) and aligns with Livepeer’s vision of future-proof, AI-ready docs. I look forward to collaborating with the Livepeer team & community to make this project a success.

Livepeer / Internal References

  1. Livepeer RFP — Documentation Restructure
    The main RFP document you’re responding to. It defines the objectives (“stakeholder-focused, AI-first, future-proofed”), personas (developers, delegators, gateway operators, orchestrators), and the problem areas.

  2. Livepeer Cloud SPE Proposal
    A proposal that includes documentation goals: “Clear and easy documentation for a go-Livepeer Broadcaster”, etc. Useful as an example of scope and deliverables in Livepeer ecosystem.

  3. “How to propose changes to Livepeer’s Documentation”
    Shows the existing contribution model and process around documentation changes. It can help show you understand the workflows in place.

  4. Open Source Funding SPE
    A proposal focused on supporting open-source projects. Can illustrate how Livepeer values documentation and infrastructure work in the broader context of ecosystem support.

External / Best Practices References

  1. Diátaxis Framework
    (Mentioned in your draft approach) — an established method for structuring technical documentation into tutorials, how-tos, conceptual docs, and references. While not a Livepeer document, this is a recognised best practice in developer docs design.

  2. WCAG Accessibility Guidelines
    Ensures your documentation is usable for people with disabilities. Many organisations treat WCAG (Web Content Accessibility Guidelines) as standard. Including this shows attention to usability.

  3. SEO Best Practices / Metadata / Semantic Markup
    Applying semantic headings, URL structures, meta tags, sitemaps, etc. are general best practice for documentation and websites. You can mention references from Docusaurus or Mintlify docs about how metadata helps with search/discoverability.

  4. Community Feedback / Forum / GitHub Issues
    The plan to aggregate questions from Livepeer’s forum, Discord, GitHub (to capture content gaps) is aligned with community-driven documentation improvement practices used in many open source ecosystems.