Well, you may (or may not) be happy to know that since launching the LearnDash WordPress LMS, we have successfully debunked the most common criticism we have come across since starting this project last year. Sure, there will always be doubters — and that’s fine. In fact, using WordPress as an LMS isn’t the right choice for every situation. But still, it feels good to put this one to bed.
Since the LearnDash adventure began last March (at the time called “WPLMS”), we received plenty of encouragement from the community. The buzz proved that there were people starving for a solution of this nature. Developers were contacting us weekly to inquire about how they could help and suggesting possible features. Small businesses and non-profits were sending us emails inquiring the same. It was all very exciting, and we couldn’t wait for everything to take shape. However, for some reason, many e-learning professionals were extremely skeptical, some downright negative.
I was actually quite disappointed about this as I have made a career in this industry and could clearly see the positives of interjecting WordPress into e-learning. Personally, it seems almost more difficult to make an argument against it. Nonetheless, there were (and still are) naysayers. Without fail the biggest backlash against using WordPress for learning management purposes was because it lacked the “traditional SCORM support” offered by mainstream open-source LMS packages such as Moodle.
To tell you the truth, we actually looked very seriously at this one. I spoke to development about SCORM, its purpose, why we use it in the learning industry and made a general case for why we should push forward with including it. As time went on though, we began to see why SCORM is often missing from a lot of software packages today… it’s clunky, not mobile compatible, and flat-out dated.
TinCan to the Rescue
All seemed about lost until TinCan API emerged. To tell the truth, I had heard about this new learning protocol, but never really did extensive research as it wasn’t even part of the most common rapid e-learning tools. Programs like Articulate and Captivate were chugging along with new features and versions, all of which remaining true to SCORM 2004. After jumping onto the phone with some industry experts, reading high-level descriptions and detailed specification documents, the answer became clear:
We don’t need SCORM in our LMS.
TinCan API makes it possible for e-learning (or any learning for that matter) to “live” anywhere, and as a result, it can be hosted and launched on WordPress! Now that rapid e-learning giants like Articulate and iSpring are jumping on board with TinCan, the days of SCORM are numbered. It will take time for SCORM packages to be a thing of the past – in fact, it still has some use. As with any industry though, the emerging trends will eventually become the expectations. TinCan will be expected (even demanded) because of the flexibility it allows instructional designers, LMS administrators, and organizations as a whole.
The biggest complaint about using WordPress as a learning management system was that it didn’t properly conform to the industry standard protocol (SCORM at the time) for e-learning development. That is no longer true. Using TinCan in conjunction with WordPress, such as the way LearnDash does, allows for rapid e-learning courses to find their home on a WordPress site. Admins can then supplement their LMS functionality by leveraging the thousands of free plugins available, the enormous support community, and tens of thousands of themes. The learning curve is cut in half, and the smooth “cool” factor that comes with WordPress is now available in the e-learning world – oh how we live in exciting times!
Rest in peace old #1 myth – you won’t be missed 😉