Hi Livepeer team,
We’re excited to further our contribution to the Foundation through this RFP proposal and would be delighted to help you and the builders out there looking to take advantage of your technology. Please see the proposal from Myosin below:
Background
Livepeer Foundation stewards the long-term vision, ecosystem growth, and core development of the Livepeer network. Following the creation of the core network architecture by Livepeer Inc and the community-governed treasury, the launch of the LF marks a new chapter in the progressive decentralization of the Livepeer project.
The Foundation’s role is to ensure that the Livepeer project builds a thriving ecosystem of founders, applications, and gateways alongside a highly-performant, capable, and secure network that is truly accountable and governed by token holders. In order to do that, LF needs excellent relations with developers and that can often start with well laid out and organized technical documentation.
The Brief
Livepeer Foundation has tasked Myosin with completely overhauling their documentation system, through a publicly available RFP. The goal is to create a stakeholder-focused, AI-first documentation structure, modernize content for all user personas, and establish sustainable maintenance processes to drive growth for the ecosystem.
The Strategy
Myosin has been refining a marketing playbook that improves brand awareness, drives community engagement and accelerates user adoption.
Documentation Architecture Redesign
We’ll conduct a comprehensive audit of existing documentation, identifying gaps, redundancies, and outdated content (we often receive praise for how thorough our work is on auditing, which isn’t the exciting work but it’s so important).
Where appropriate, we’ll verify key gateway references by running them against staging to validate core flows.
Develop a new Information Architecture
Working closely with key stakeholders, we’ll develop a new information architecture that prioritizes user journeys for developers, delegators, orchestrators, and gateway operators.
This restructuring will create clear entry points for each persona while maintaining cross-cutting resources that benefit all users.
Gateway Documentation Audits & Standards (link-out model)
In line with the RFP’s single-source-of-truth and no-duplication goals, we will not host partner API docs on the Foundation site. Instead, we will:
-
Audit 3–4 gateway/provider documentation sets and produce summaries.
-
Define “Docs Standards for Gateway Partners” (IA, naming, versioning, searchability, error patterns).
-
Implement a clean link-out model from Foundation docs to Gateway Partner docs once standards are met, with clear attribution.
Technical Writing
We will prioritize the top 1–2 personas and deliver a great Transcoding Quickstart experience. The audit and IA will cover all personas (Developers, Delegators, Orchestrators, Gateway Operators); non‑priority personas receive structural updates, and deprecations/redirects. Within the core timeline, we’ll deliberately balance effort across three tracks rather than trying to do everything at once:
(1) Studio → Gateway migration: an agnostic guide mapping Studio concepts/flows to current stakeholder gateways, with standards‑based link‑outs (no duplicate hosting)
(2) Targeted API/SDK references added where needed
(3) Light‑touch updates (where needed) to core pages (e.g., Getting Started, Core Concepts): accuracy fixes, deprecations/redirects, IA alignment.
The audit will determine exact priorities. If time allows within the core timeline (after other core deliverables), we can expand to additional tasks.
We will build a foundation of well structured, human-readable documentation and future-proof this by using clean semantics and logical headings. This foundation will be possible to deliver within your timeline and can then be layered with AI features built on top of a stable base.
Sustainable Documentation Governance
Beyond just creating content, we’ll establish the systems and processes needed for long-term documentation health. This includes developing style guides, contribution workflows, and ownership models that ensure consistency and quality over time.
We’ll work with the Livepeer Foundation to create clear maintenance protocols that enable both internal teams and community contributors to participate in documentation upkeep.
Objectives and Key Results (OKRs)
The key objectives of this project are to restructure the documentation architecture, modernize content for all user personas, and establish sustainable maintenance processes for Livepeer Foundation.
This project will be assessed by the following metrics:
-
Reduction in support tickets related to documentation confusion
-
Establishment of clear contribution workflows with measurable community participation
-
Zero broken links on all pages we create or edit; redirects added for any moved/renamed pages; out-of-scope issues documented with recommendations.
-
Decouple protocol docs from gateway-specific APIs; implement a standards-based link-out model to partner docs (no duplicate hosting)
Our Proposal
We propose a project to completely transform Livepeer’s documentation system with a focus on stakeholder needs, AI-readiness, and sustainable governance.
Documentation Strategy & Architecture
-
Internal docs audit (Foundation) with stakeholder‑specific recommendations
-
Development of new information architecture with clear user journeys
-
Creation of a consolidated changelog and versioning system
-
Gateway/provider docs audits (3–4) with summaries and “Docs Standards for Gateway Partners”; implement link-out IA and attribution
-
Draft a forum post detailing the changes to get feedback and generate excitement from the community
Content Development & Modernization
-
Comprehensive rewrite of core documentation for the top 1-2 primary stakeholder groups
-
Creation of goal-oriented Quickstarts for Transcoding Jobs
-
Studio → Gateway migration (most common path): an agnostic guide that maps Studio concepts/flows to current gateways, with link‑outs to partner documentation that meets Foundation standards. No duplicate hosting of partner API docs.
-
Audit and scaffold API/SDK sections; integrate existing API references and SDK links via link-outs to gateway/provider docs.
-
Work with existing groups (Livepeer Inc, AI SPE, Cloud SPE, and gateway providers) to incorporate their starter repos, copy‑paste snippets, and full API/SDK/CLI references via a standards‑based link‑out model; we do not duplicate or host partner API docs.
Governance & Sustainability Framework
-
Creation of documentation style guide and voice/tone guidelines
-
Documentation of suggested workflows and PR templates
-
Establishment of ownership and review processes
-
Planning and recommendations around documentation analytics and feedback systems
Project Plan
PHASE ONE (Documentation Strategy & Planning)
We’ll conduct a thorough assessment of the current documentation landscape and develop a comprehensive strategy for restructuring.
Week 1: Stakeholder interviews and documentation audit
-
Conduct interviews with key stakeholders (Livepeer Foundation, Livepeer Inc, AI SPE, Cloud SPE, etc.)
-
Complete comprehensive audit of existing documentation
-
Identify gateway contacts; request access to their docs/specs.
-
Identify core user journeys and pain points
Week 2: Information architecture development
-
Create new documentation structure with clear stakeholder entry points
-
Begin gateway early evaluations (rapid triage for 3–4 gateways), start early “Docs Standards for Gateway Partners”
-
Develop sidebar, taxonomy, and breadcrumb structure
-
Plan for consolidation of changelogs and versioning system
Week 3: Strategy finalization and RFC
-
Finalize documentation strategy with stakeholder input
-
Prepare forum post for community RFC
-
Establish project management processes and tools
-
Present new documentation strategy (Due: October 17th)
PHASE TWO (Content Development)
We’ll systematically work with core stakeholders to rewrite and restructure content to align with the new architecture and meet stakeholder needs.
Week 4-5: Core content development
-
Begin rewriting/editing documentation for primary stakeholder groups
-
Develop/edit Quickstart for Transcoding Jobs
-
Gateway partner working sessions on must‑fix items
-
Deliver ongoing rolling gateway summaries
Week 6-7: Advanced content development
-
Implement link-out IA and attribution from Foundation docs
-
Integrate targeted references where needed
-
Complete first draft of documentation (Due: November 7th)
PHASE THREE (Implementation & Governance)
We’ll implement the new documentation system and establish processes for long-term maintenance.
Week 8: Technical implementation
-
Deploy redesigned IA and content in current docs stack
-
Set up redirects and ensure zero broken links
-
Launch V1 documentation (Due: November 14th)
Weeks 9-12: Governance and handover
-
Develop style guide and contribution guidelines
-
Create PR workflow for community involvement
-
Establish ownership and review processes
-
Complete governance framework and handover (Due: December 5th)
This timeline is approximate and subject to change based on stakeholder feedback and technical considerations. Some examples of delays could be client-side decision-making or coding bugs uncovered that require engineering fixes.
We will work closely with the Livepeer Foundation team throughout to align on priorities and optimize based on learnings.
Your Myosin Team
Your Myosin team will be assembled from our global network of documentation specialists, technical writers, and DevRel experts. We’ll provide a dedicated team with experience in blockchain documentation, developer experience, and technical content creation.
Bettina Sosa - Technical Designer
Bettina Sosa is a software engineer, designer, and Web3 builder with deep expertise bridging development, technical advocacy, and product innovation, with award-winning design work. Her roots span full-stack engineering and design, and her passion is combining software, cryptography, and user experience to build next-gen systems. She was the founding full-stack engineer at Sojo, responsible for designing, developing, and deploying the company’s core platform for on-demand clothing repairs and customizations. She later joined Catapult Labs as a founding full-stack engineer, where she developed the company’s flagship Web3 profiles platform for decentralized networking and went on to design decentralized financial primitives (including OTC crypto markets, collateral management, and margin trading systems).
Bettina currently leads Developer Relations at Myosin as a Guild Lead. More recently, Bettina has focused on developer relations, cryptographic systems, and community growth. She served as Head of Engineering & AI at Partisia Blockchain, combining cryptography, MPC, and AI to expand its engineer ecosystem. Her fluency in Rust, Solidity, TypeScript, product design, and community engagement, (along with bilingual fluency in English and Spanish), positions her as a powerful bridge between deep tech and developer outreach.
Valentina Rivas — Technical Writer
Valentina Rivas is a security and blockchain researcher, software engineer, and technical writer with a proven track record of delivering high-impact research and developer-focused content. She specializes in blockchain research, applied cryptography, and blockchain data analytics across the EVM and Solana ecosystems. Her portfolio includes technical coding tutorials for Cyfrin, deep-dive research and data engineering work for The Rollup (covering tokenized assets, stablecoin dynamics, cryptography adoption, etc), and hands-on cryptography tools such as BLS Lab, which demystifies BLS signatures, Shamir’s Secret Sharing, and hashing for developers and non-technical audiences alike. Her tutorials have been officially featured on Ethereum’s Developer Tutorials website section, and her research + coding guides have been cited in U.S. public policy letters.
Valentina also serves as Developer Relations Guild Lead at Myosin, helping shape the guild’s strategy and initiatives for technical content and community growth. With multiple hackathon wins, analytics bounties, and top-ranked dashboards under her belt, Valentina blends technical rigor with accessible communication. She is fluent in English and Spanish, experienced in Solidity, Python, JavaScript/TypeScript, SQL, and advanced analytics platforms, helping organizations strengthen their security posture, improve developer experience, and communicate complex blockchain concepts with clarity.
Romulo Castilho - Creative Director (Project Sponsor)
-
Myosin Design Guild Lead, Ex FutureBrand, and Design Bridge Creative Director
-
Previous Clients: Polygon, XRP, NEAR, Animoca, Google (Asia), Nestlé, Chope (APAC), Bukalapak (Indonesia)
Pricing & Payment Terms
$25k flat fee for project completion, which includes;
-
Full documentation audit and strategy development
-
Information architecture redesign
-
Content rewriting for top 1-2 stakeholder groups
-
Implementation in current docs stack
-
Governance framework and workflows
-
Weekly progress updates and stakeholder alignment
-
Includes up to 3 feedback rounds per deliverable
-
Scope beyond this can be scoped separately
Payment Terms:
Important notes
-
Assumptions & dependencies: Assumes stable APIs/SDKs and provisioned test credentials. If blocking bugs are found, timelines pause until fixes are available.
-
Client-side responsiveness: Our ability to hit timelines depends on prompt feedback from Client. If a document is sent for review and it takes 1–2 weeks to respond, the project will stall. The same applies to technical questions (API/SDK/core concepts), quick answers are key to our speed. We’ll clearly communicate what we need and when we need it to avoid bottlenecks.
-
Partner docs: We will not author or host partner API docs. We provide audits, standards, and link-outs; partners implement changes on their sites.
-
Gateways: By default we do not link to gateways that haven’t met Docs Standards. If the Foundation prefers to link anyway, we can include a disclaimer badge (“Docs in progress”/”Pending updates”) per gateway. We provide their scorecard/summary and must‑fix recommendations.
Optional Add Ons
Custom Video Tutorials - $5,000 Development of 5 professional tutorial videos to complement written documentation. These could be interactive discussions or single person dev rel reviews, uploadable to your chosen social channels.
AI-First Content Development - $5,000 Our approach centers on creating documentation that’s not only human-readable but optimized for AI consumption. We’ll implement semantic headings, structured metadata, and machine-readable references throughout. By integrating natural language search capabilities and ensuring content is properly structured for LLM parsing, we’ll create a documentation system that leverages the latest in AI technology to enhance user experience.
Attribution reporting - TBD Generate reporting to show traffic Livepeer Foundation is delivering to its Gateway Partner docs websites.
Next Steps
-
Await Livepeer Foundation decision (available for further qualifying calls if needed)
-
Finalize contract and scope of work
-
Begin stakeholder interviews and documentation audit
About Myosin.xyz
What is Myosin.xyz, and why are they so good at what they do?
Myosin.xyz is a web3 native marketing network, made of 60+ members across 26 countries.
As a cooperative (some might say DAO), we unite the best marketers from around the world to provide full-stack marketing services to onchain companies & blockchains such as Ripple, NEAR, Starknet, Solana Mobile, Chainbase, POKT Network, Animoca Brands, Rootstock Labs, and many more.
We have 5 core offerings:
-
GTM & Growth
-
PR and KOLs
-
Brand design, video, animations, 3D, & creative
-
Community, social media, content, & research reports
-
DevRel and technical writing
Myosin’s mission is to become an aggregator of the world’s most innovative marketing tactics, and our community of highly vetted talent consists of strategists, creatives, deal makers, developers, growth hackers, and more, all of whom are dedicated to accelerating the adoption of the new internet.
Look forward to working with the community here! 
