Forum Discussion
Using Videos in Code Blocks in Rise
I've seen examples of AI Avatar videos being embedded in code blocks within Rise. How are you hosting them? I love the idea, but I'm unsure how to host the videos so I can just share a link to embed in the code.
Good answers above already — I'll add the decision criteria I use in corporate training, since where you host changes more than just the URL.
If you bundle the video inside the code block project (DShaw's zip approach): everything travels with the course. That's great for LMS portability — no external dependency to break, and no firewall surprises for learners on locked-down networks. The tradeoffs: every video update means re-zipping and republishing, and large video files inflate the course package.
If you host externally (Vimeo, YouTube, your intranet): you can swap the video anytime without republishing, which is handy for AI avatar content that gets regenerated often. The tradeoffs: the course now depends on that link staying alive, learners behind corporate firewalls may not be able to reach it, and — the big one in my world — uploading internal training videos to public platforms can be a policy problem. Unlisted is not private, so check with your org before anything proprietary goes on YouTube or Vimeo.
Rule of thumb I use: bundle it when the video rarely changes and your learners are on managed devices; host externally when it changes often and the platform is approved. Either way, test from an actual learner's device and network before you call it done.
3 Replies
The embed code is more just a part of standard HTML: <embed> HTML embed external content element <embed> can actually accept a hyperlink to a variety of file types, including audio, documents, and other .story/.html files. Just depends on if the file is accessible to the Rise course.
A video can be hosted most any web server. It could be Vimeo, YouTube, a personally-hosted site, or even a company intranet so long as again the Rise course can access it.
Alternatively just use the upload project code block and zip the video file along with your index.html file and upload…
Good answers above already — I'll add the decision criteria I use in corporate training, since where you host changes more than just the URL.
If you bundle the video inside the code block project (DShaw's zip approach): everything travels with the course. That's great for LMS portability — no external dependency to break, and no firewall surprises for learners on locked-down networks. The tradeoffs: every video update means re-zipping and republishing, and large video files inflate the course package.
If you host externally (Vimeo, YouTube, your intranet): you can swap the video anytime without republishing, which is handy for AI avatar content that gets regenerated often. The tradeoffs: the course now depends on that link staying alive, learners behind corporate firewalls may not be able to reach it, and — the big one in my world — uploading internal training videos to public platforms can be a policy problem. Unlisted is not private, so check with your org before anything proprietary goes on YouTube or Vimeo.
Rule of thumb I use: bundle it when the video rarely changes and your learners are on managed devices; host externally when it changes often and the platform is approved. Either way, test from an actual learner's device and network before you call it done.
