I am using the authoring tool v0.8.1
Given the following scenario I'm wondering what everyone in this community thinks about my approach and if there may be a better way to accomplish what I'm after.
Background & problem: I have a lot of training material written in markdown format. I want to create SCORM packages out of this content and upload it to an LMS using adapt authoring. I was hoping to upload the markdown files themselves directly into a component/extension/plugin that would properly translate them into html on the fly when displayed in the course, but as near as I can tell that doesn't exist. I could do the manual work of copying the content into the built in components/extensions/plugins that are available in the authoring tool, but this is a lot of work for me and I can't help but to think there's a better way. There are also other reasons for keeping the content itself in markdown format for other purposes.
Even with this solution there are still challenges around the use of the iframe component where my height is going to be dynamic depending on which chapter of content is currently being displayed. I think I can work around this with some fancy and as usual annoying css, however, this is just one more thing that leads me to believe that I'm making something that should be very simple, way too complex.
1. is what I'm doing really stupid? Should I just suck it up and maintain two formats of my training material? 1 copy in markdown format, another in customized scorm packages?
2. what's the recommended best way to solve this problem?
3. Is there a plugin out there that I don't know about that will actually take markdown as input, and convert that to html, thereby negating the crazy noted above?
I am using the authoring tool v0.8.1
There are extensions which convert other formats at run time. e.g. MathJax
This works pretty well. I expect you could do the same sort of thing for mark down.
Maybe https://github.com/markedjs/marked for example.
Sounds interesting. Let me know how you get on.
I'd be more tempted to create something that translated markdown into adapt JSON but without being able to see your content it's very hard to judge what the best way would be.
Otherwise it seems like you're just using Adapt as a kind of 'SCORM container' - which feels like a very heavy-handed way of doing what you need - or are you mixing this content in with other adapt content? If not and your aim is just to take some markdown, convert it to HTML and make it SCORM compliant there's surely easier ways of doing that.
thank you both for the replies. I do have a few videos, at least two 'hot graphics' and a number of test questions per module that I had planned to use the Adapt authoring core plugins for. I've been told I have to have everything in an LMS for a few different reasons, so wrapping the content in SCORM packages seemed logical, otherwise I feel I'm locking my company into our LMS and for a variety of reasons I want to try and avoid that. Thanks again for the replies....I'll see what I can figure out...
I do have a few videos, at least two 'hot graphics' and a number of test questions per module that I had planned to use the Adapt authoring core plugins for
Ah OK I see makes sense now
Is using the Framework directly rather than the Authoring tool an option? Just thinking you could do something clever in the build process that converted markdown into JSON... Obviously depends enormously on how comfortable you are with coding that sort of thing. And whether it's possible to map the content you have in your markdown to Adapt components...
yeah good idea - I think the content needs to go into the body section of a json file - I forget exactly which one but I found it earlier. It's not impossible but it seems to me an error prone process; as we would need to put the content into that field according to both html and json formating...I might be able to link a library for markdown to html but then going to json is yet more work. So far I've found using the 'source' feature of the text component and pasting in html there (converted outside of Adapt) works well enough. It's far from automated but I think I can live with it. Thanks again for all the replies...
ok so I wanted to circle back on this. I have stitched together a few open source tools to accomplish this, documenting here in case others find it useful. The majority of my training material is in markdown format. I've got each markdown file setup to represent a different module of my training course, and the idea was that each of these will become their own scorm package for upload to our LMS. Doing it this way allows me to have one source format and output to 2 (or more) different formats, which is necessary for me as I definitely see a time when either one of my company's customers or a member of my executive team asks me for a simple, single document that contains all my training material. If I've got nothing but a bunch of custom scorm packages I can't easily do this, but if the source content is kept in markdown I can do both with _relative_ ease.
# quit if input isn't a directory
if [ ! -d "$1" ]
echo 'input not a directory. Input directory must contain 1 or more markdown files with an .md extension'
for f in $1/*.md
marked $f > $f.html
json_encode.php $f.html > $f.html.json
json_encode.php reads as follows:
$html = file_get_contents($argv);
the resulting input.md.html.json file is manually copied into the body tag of the components.json file in the src/course/en folder of my course.
My content contains images, and I've made this work by ensuring I reference them using relative paths to course/en/images. non-relative paths will work in the "grunt server" preview using the Adapt framework, but _will not_ in my LMS - only the relative path works.
So there it is....I hope this is useful to someone. Scorm is great and all, but if all your content is only in that format...as near as I can tell you would be limited to having your training content in an LMS - you couldn't easily make a simple document out of the same content. Maybe this is way overkill, maybe not...I'm honestly not sure, but at the very least, perhaps this info will be useful to someone...
Yes, SCORM is very much focussed on dealing with web content, in a browser, hosted on an LMS. Given that the SCORM standard was first developed in 2000/2001 it's often not that practical in the modern world - but it is still the most supported format!
You might like to take a look at xAPI if you need something a bit more flexible.