I design the lesson,
then build the pipeline that ships it.
Parth Dhanani
Instructional designer and learning engineer at Kidvento, Mysore. Open to remote roles worldwide.
Results
what changed because of the work- 100+
K-12 SCORM modules shipped by my team
Kidvento, team of 8
How we know
Team output, not a solo count. I lead four developers and four interns and built the pipeline they ship through. Client modules are not public.
- 300+
Quizzes, simulations and activities for a state K-12 curriculum
Learning Lozix, 2019 to 2022
How we know
Storyline 360 builds for Balbharati, the Maharashtra state K-12 standard, each with a WCAG 2.1 check. A reusable JavaScript interaction library cut build time. Modules are not public.
- 6
Languages localized from one master file
Learning Lozix and Learning Owl
How we know
Hindi, Tamil, Kannada, Punjabi, Gujarati and Telugu. Separately at Kidvento: Hindi and French video with HeyGen and ElevenLabs, no re-recording on camera. See the localization case study.
- 4h to 10m
Publishing time per package
scorm-kit
How we know
Measured on a clean Storyline package. Anything QA sent back restarted the four hours, which is why the tool exists. scorm-kit has 32 tests passing.
- 3 to 1
Visual revision rounds per module
Learning Owl
How we know
After replacing manual asset handoff with an Illustrator to Storyline workflow.
Work
pick your problem, or read all fiveEvery tool here exists because a manual step kept failing. The failed attempts stay in.
Or open any thread:
Training that changes behaviour, not just a quiz score
The same 3 questions before any slide now drive every compliance course I build.Design
- failed
Starting from a 90-minute PowerPoint brief. "They would know X" is not a behaviour. - failed
Slides of facts with a quiz at the end. People pass the quiz and change nothing. - worked
Asking the three questions until a behaviour appears, then building branching scenarios around it.
Publishing a package by hand took 4 hours
Publishing went from 4 hours to 10 minutes per package.Build
- failed
An eight-step manual checklist. Fine at 10am, unreliable at 6pm. - failed
Asking people to be more careful. The skipped steps were the boring ones a script never skips. - worked
A Node CLI that patches the manifest, injects the reporting hook and fixes the completion flag the same way every time, with a deterministic re-zip.
Writers waited on developers to see their own storyboard
A Markdown storyboard becomes an uploadable SCORM zip with one command.Build
- failed
Re-typing every storyboard into Storyline. Storyboard and build drifted apart at the first review comment. - worked
Storycraft: the storyboard is the source, the package is a build output. Six languages are six Markdown files and one command.
Video buffered on slow school networks
3 bitrates in one zip, nothing for a school to install.Ship
- failed
One low-resolution master. It fixed the buffering and ruined the lesson for schools on a good connection. - failed
An HLS variant. It worked in isolation, then failed on three target LMSs that served .m3u8 with the wrong MIME type. - worked
Three FFmpeg variants inside the SCORM zip, and a bandwidth probe at launch that picks one before playback starts. Try it under Play.
A freeze nobody could reproduce
The freeze is fixed, and the build now fails on duplicate IDs.Ship
- failed
Re-publishing and clearing school caches. It helped just long enough to look like a fix. - failed
Blaming the LMS while the LMS team blamed Storyline. The bug hid there for weeks. - worked
Logging every SCORM API call and watching two learners reproduce it live.
cmi.interactions.N.idwas written twice, and the LMS was right to reject it.
Play the work
runs in your browser, no LMS, no sign-up
Why you fall forward when the bus stopsPlay the lesson here
scorm-kit build report
100 / 100Lint, accessibility and privacy: 0 errors, 0 warnings.
Five more modules, all built with Storycraft
-
What You Didn't Say
-
The First Page
-
Why Negative × Negative = Positive
-
Workplace Respect, POSH Awareness
-
कार्यस्थल पर सम्मान, POSH
Same button, six languages
Three bitrates, one zip
About
8+ years in eLearning
I lead the eight-person SCORM team at Kidvento.
Before any slide, three questions: what is the person doing six months later, where do people most often get it wrong, and if only one decision could be trained, which one.
- Jan 2025 to nowKidvento (Ulipsu), Learning Engineer and SCORM Team Lead. Master Mentor Certificate, Mar 2026
- 2023 to 2024Learning Owl, Instructional Designer and eLearning Development Lead
- 2019 to 2022Learning Lozix, eLearning Developer and Content Designer
- 2018Lionbridge, Localization Integrator (contract)
- 2015 to 2017Freelance, content and motion design
Toolkit
- ADDIE
- Action Mapping
- Storyline 360
- Rise 360
- SCORM 1.2
- xAPI
- WCAG 2.1/2.2
- JavaScript
- Python
- FFmpeg
- HeyGen
- ElevenLabs
- Moodle
- Illustrator
- Figma
Tools
built and tested| Tool | What it does | Tests | Links |
|---|---|---|---|
| Storycraft | Markdown storyboard in, SCORM 1.2 package out | 11 passing | Case studySource |
| scorm-kit | Validates, patches and re-zips SCORM packages | 32 passing | Case studySource |
| xapi-doctor | Checks xAPI statements against 30 spec-cited rules | 17 passing | Source |
| courselint | Scores a SCORM course 0 to 100 on the Quality Matters rubric | Self-check passes | Case study |
| EAA Checker | WCAG 2.2 and EAA report for a SCORM zip | None yet | Source |
| SB Translation Tool | Moves quiz text between PPTX, Storyline and translation docs | None yet | Open the appSource |
Contact
email is fastest- Email[email protected]
- LinkedInlinkedin.com/in/dhananiparth
- GitHubgithub.com/parthdhanani
- ResumeDownload the PDF, 29 KB