Parth Dhanani

I design the lesson,
then build the pipeline that ships it.

Parth Dhanani

See what I build

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 five

Every 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
One decision splits into two choices, and each choice plays out its own result. One decision Choice A Choice B its result its result
A branching scenario: the learner makes the call, then sees what it costs.
  1. failed

    Starting from a 90-minute PowerPoint brief. "They would know X" is not a behaviour.

  2. failed

    Slides of facts with a quiz at the end. People pass the quiz and change nothing.

  3. worked

    Asking the three questions until a behaviour appears, then building branching scenarios around it.

Read the design notes

Publishing a package by hand took 4 hours

Publishing went from 4 hours to 10 minutes per package.Build
  1. failed

    An eight-step manual checklist. Fine at 10am, unreliable at 6pm.

  2. failed

    Asking people to be more careful. The skipped steps were the boring ones a script never skips.

  3. 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.

Read the build

Writers waited on developers to see their own storyboard

A Markdown storyboard becomes an uploadable SCORM zip with one command.Build
  1. failed

    Re-typing every storyboard into Storyline. Storyboard and build drifted apart at the first review comment.

  2. worked

    Storycraft: the storyboard is the source, the package is a build output. Six languages are six Markdown files and one command.

Read the case study

Video buffered on slow school networks

3 bitrates in one zip, nothing for a school to install.Ship
  1. failed

    One low-resolution master. It fixed the buffering and ruined the lesson for schools on a good connection.

  2. failed

    An HLS variant. It worked in isolation, then failed on three target LMSs that served .m3u8 with the wrong MIME type.

  3. worked

    Three FFmpeg variants inside the SCORM zip, and a bandwidth probe at launch that picks one before playback starts. Try it under Play.

Read the build

A freeze nobody could reproduce

The freeze is fixed, and the build now fails on duplicate IDs.Ship
The SCORM call log. The same interaction ID is written twice for the same interaction. The LMS accepts the first write and rejects the second, so the Next button never turns on. SCORM call log set interaction N id accepted set interaction N id rejected same N, written twice: Next stays off
The second write of the same ID froze the lesson.
  1. failed

    Re-publishing and clearing school caches. It helped just long enough to look like a fix.

  2. failed

    Blaming the LMS while the LMS team blamed Storyline. The bug hid there for weeks.

  3. worked

    Logging every SCORM API call and watching two learners reproduce it live. cmi.interactions.N.id was written twice, and the LMS was right to reject it.

Read the diagnosis

Play the work

runs in your browser, no LMS, no sign-up
Why you fall forward when the bus stops

Physics, sample lesson. Plays right here, no LMS and no sign-up.

Play the lesson here

scorm-kit build report

100 / 100

Lint, accessibility and privacy: 0 errors, 0 warnings.

Five more modules, all built with Storycraft

  • First screen of the module: Before we start, with a Next button.

    What You Didn't Say

    Soft skills, 18 min

    PlaySCORM zip

  • First screen of the module: This is not the runbook, with a Next button.

    The First Page

    Technical, 20 min

    PlaySCORM zip

  • First screen of the module: The question your teacher never answered.

    Why Negative × Negative = Positive

    K-12 math, 12 min

    PlaySCORM zip

  • First screen of the module: Welcome, with three learning objectives.

    Workplace Respect, POSH Awareness

    Compliance, 15 min

    PlaySCORM zip

  • First screen of the Hindi version of the module, with a Hindi welcome heading.

    कार्यस्थल पर सम्मान, POSH

    Compliance, Hindi

    PlaySCORM zip

Same button, six languages

Show the button in
Continue

Three bitrates, one zip

A probe at launch measures the connection and picks one of three video variants packed in the SCORM zip: low, medium or high bitrate. Probe inside the SCORM zip low medium high

About

8+ years in eLearning
Parth Dhanani, head and shoulders, in a dark T-shirt against a plain light wall.
Parth Dhanani, learning engineer

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.

  1. Jan 2025 to nowKidvento (Ulipsu), Learning Engineer and SCORM Team Lead. Master Mentor Certificate, Mar 2026
  2. 2023 to 2024Learning Owl, Instructional Designer and eLearning Development Lead
  3. 2019 to 2022Learning Lozix, eLearning Developer and Content Designer
  4. 2018Lionbridge, Localization Integrator (contract)
  5. 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
ToolWhat it doesTestsLinks
StorycraftMarkdown storyboard in, SCORM 1.2 package out11 passingCase studySource
scorm-kitValidates, patches and re-zips SCORM packages32 passingCase studySource
xapi-doctorChecks xAPI statements against 30 spec-cited rules17 passingSource
courselintScores a SCORM course 0 to 100 on the Quality Matters rubricSelf-check passesCase study
EAA CheckerWCAG 2.2 and EAA report for a SCORM zipNone yetSource
SB Translation ToolMoves quiz text between PPTX, Storyline and translation docsNone yetOpen the appSource

Contact

email is fastest