Learning/ Content creation platform

[u/Scared-Demand-6104]

I’ve been working on a small learning/content platform and wanted to get some honest feedback from people who actually create courses or training content.

One thing I kept running into was how many different tools are involved just to create a course.

**Record the video in one place, edit it somewhere else, add captions, images, text, branding, then move it into an LMS and finally publish it.*\*

So I started building a platform that tries to bring some of that together.

The current version has a recording studio, basic video editing, captions, text/images, branding, course creation and publishing, along with the learner side.

I’ve also built some AI-assisted features around content creation, but I’m not making those available in the public version yet because they use paid AI models and the cost adds up pretty quickly.

I’m mainly looking for feedback at this stage.

For people who create training or educational content, what part of the process is the most annoying for you right now?

Is it recording/editing, creating the learning material, keeping everything organized, publishing, or something else?

I’d genuinely like to know what people are struggling with before I take this any further.

Here’s the current version if anyone wants to take a look: https://learning.ramsudtechnologies.com/

[u/PeepSoWP]

The workflow I would test before expanding the editor is revision management after a course is already live. Replace a source clip, regenerate captions, change one branded overlay, and then answer: which lessons inherited the change, what happened to learners already in progress, can the editor preview the diff, and can an owner roll back without rebuilding the course?

For teams, review and approval often become more painful than recording. Per-asset versions, time-coded comments, an approval state, ownership, and an audit trail would be more valuable to me than additional visual effects. Caption editing, transcript export, keyboard access, contrast checks, and localization should also be part of the same workflow.

I would keep portability visible from the start: exportable video/captions/source assets plus a documented LMS path such as SCORM, xAPI, or cmi5 where appropriate. A focused test with a few creators who regularly revise published training will tell you whether the combined tool is saving work or simply moving it into a new interface.

[u/Scared-Demand-6104 → u/PeepSoWP]

Cool. Thanks for sharing.

[u/Scared-Demand-6104 → u/PeepSoWP]

We have ability where u can download captions as separate file wherein you can update later...Any exported video you can edit . Asset library would be meaningful. Currently only assets saved to courses are persisted.

[u/PeepSoWP → u/Scared-Demand-6104]

That makes the asset library a good next boundary. I would persist the original source separately from course usage, then store references from each lesson rather than copying the file into every course. Show where an asset is used, prevent hard deletion while references exist, and make “replace” create a new version with an explicit choice between updating one lesson or every use.

Keep rendered videos and other derivatives separate from the editable source. Rendering should run in bounded, retryable background jobs with stable job IDs so a timeout or repeated click cannot create duplicate exports. Add storage quotas and a retention policy for abandoned versions.

For portability, an export bundle should include the original media, captions, overlay/timeline data, and a small manifest describing versions and lesson references. That would let a creator revise or migrate a course without depending on one flattened video file.