search

livepeer / livepeer-studio-docs

Livepeer Studio Documentation
https://docs.livepeer.studio
MIT License
3 stars 5 forks source link

180 Store Video Asset On IPFS #189

Closed ichung08 closed 2 years ago

ichung08 commented 2 years ago

Created new guide for how to store a video asset on IPFS

Resolves #180

vercel[bot] commented 2 years ago

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated
livepeer-studio-docs ❌ Failed (Inspect) Sep 7, 2022 at 1:04AM (UTC)
victorges commented 2 years ago

On a side note, maybe it is also a personal opinion, but I don't think it's very helpful to keep mentioning the same "technical preparation" section on all of our docs. It kind of becomes repetitive instead of elucidative, and so I just start skipping the intro sections in all our docs (which happened here then I missed the tabs).

Do we have any data from users that these intros are actually helpful? Feels like they always state some rather obvious stuff, like needing a Livepeer Stuido account and installing Node.js, so it just feels cumbersome. IMO we might be losing precious attention from the readers right here.

There has been a trend on adding that to most of our docs, so don't worry about changing everything now tho. We can just go cleaner with this one instead and progressively rewrite the others. WDYT @adamsoffer @pglowacky @Shih-Yu?

Shih-Yu commented 2 years ago

On a side note, maybe it is also a personal opinion, but I don't think it's very helpful to keep mentioning the same "technical preparation" section on all of our docs. It kind of becomes repetitive instead of elucidative, and so I just start skipping the intro sections in all our docs (which happened here then I missed the tabs).

Do we have any data from users that these intros are actually helpful? Feels like they always state some rather obvious stuff, like needing a Livepeer Stuido account and installing Node.js, so it just feels cumbersome. IMO we might be losing precious attention from the readers right here.

There has been a trend on adding that to most of our docs, so don't worry about changing everything now tho. We can just go cleaner with this one instead and progressively rewrite the others. WDYT @adamsoffer @pglowacky @Shih-Yu?

Agreed if you think it will lose the attention of the readers. Should we also change export to IPFS to store on IPFS or something to this effect?

ichung08 commented 2 years ago

Thanks for all the comments! I've updated the PR accordingly

pglowacky commented 2 years ago

I don't think it's very helpful to keep mentioning the same "technical preparation" section on all of our docs.

Agree. Let's remove this section moving forward.

Should we also change export to IPFS to store on IPFS or something to this effect?

I don't think we should say export here -- users want to pick storage not export their asset elsewhere. Additionally, there is (I believe it's currently undocumented) API endpoint for export that allows users to send an asset (like a recording) to a URL for storage. I don't want to confuse that end point with picking storage.