You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of right now, embedding a video that also exists in the repo seems to be impossible. Either we can upload videos using github's online markdown editor, but that video gets stored elsewhere (and it must be 10mb or smaller), OR we can upload videos to somewhere like youtube and embed them.
It might be possible to convert this repo into a github.io site, so we could then use perma (not relative) links to the stored location? I'll let @trallard make the final call here on what seems smartest/best.
The text was updated successfully, but these errors were encountered:
We should be able to turn this into a website to make rendering and discoverability easy.
My only concern would be if we end up with too many videos and thus blowing up the size of the repo 🤔
In which case we might need to find an alternative location, but I suppose for now we can keep them here and plan to setup a site.
Yeah, I am trying to keep most of the videos relatively small and can even capture/downscale if we want to "compress" this a little bit. It's easy to make them huge, but the short duration for most helps too.
What filesize should we try to shoot for? Or perhaps rather, what is a max repo filesize target for us?
And I did a pandoc conversion of one of the markdowns into HTML as a test and it worked perfectly, so an eventual swap to an HTML-based site wouldn't be too hard (obviously other approaches are fine too!).
As of right now, embedding a video that also exists in the repo seems to be impossible. Either we can upload videos using github's online markdown editor, but that video gets stored elsewhere (and it must be 10mb or smaller), OR we can upload videos to somewhere like youtube and embed them.
If you inspect the markdown code of this file, we should have videos shown.
The videos exist in the repo's assets now, but these don't render in github's preview of that file.
It might be possible to convert this repo into a
github.io
site, so we could then use perma (not relative) links to the stored location? I'll let @trallard make the final call here on what seems smartest/best.The text was updated successfully, but these errors were encountered: