Hi Sam, I would say in general, most eLearning Developers don't need to use JavaScript when developing content with Articulate Storyline and Adobe Captivate.
Typically there is already enough built-in functionality within the software where you don't really need to do any additional scripting. However, have said that, if you are able to learn some JavaScript, you can definitely do some additional cool things with Storyline/Captivate.
I would say to be considered a strong eLearning Developer, really focus on using the tools to their fullest (mastering triggers, layers etc...), strenghten your Instructional Design skills and creativiity, and also your visual design skills. Once you have that down, you can learn some JavaScript as the icing on the cake :)
I would add that this is not only true of those two tools, but most other authoring options out there. Generally speaking use of javascript is for edge cases.
I would say that JS is more of an exception than the norm with Storyline. It's a nice to have, when you can use it to create some neat things, but the out-of-the-box functionality is generally all that you need ;)
As mentioned by previous posters, both products are useable out of the box without having to have any knowledge of JavaScript at all.
To really shine at eLearning (imho), the key is to ensure that your instructional design is solid first. A module with 100 bells and whistles is of little value if it doesn't produce the result the client wants it to.
Consult with your client, storyboard your design ideas with them, and then when you know what you need to produce, use the eLearning tools to do so.
Sometimes the simplest modules produce startlingly effective results.
We used Captivate for years at my prior org. Only 2 of 7 IDs could really work with it. We switched to Storyline and the team was more productive month 1 than years with Captivate. It is easy for folks to build interactives. Folks more deeply skilled can toss in JavaScript for extras.
I have to agree with the others JavaScript is nice to have, but not needed for most things. Storyline is user friendly and has a lot of built in triggers and such. Solid understanding of adult learning and design are important. Also, remember that keeping it simple is often a great approach meaning your modules should be consistent and clear for the user. Solid understanding of these things along with resources like elearning heros and their challenges are a great way to build a solid understanding of the tools in storyline
Hi Sam, I don't know about Captivate but the Articulate Community really has some gems for starting developers. Obviously you need to start mastering your tools. So check out the Tutorials section to learn what you can do with Storyline. After that you should check out the weekly challenges. These are great mini-projects you can work on that help you put in the time needed to get really comfortable with Storyline without the stress of project deadlines and such. A save environment to mess up and learn!
Storyline has less of a learning curve than captivate, but is powerful enough to grow with your needs. You can build great courses without the need for javascript. Look at the tutorials on this site and get started.
We rarely use JavaScript and get on just fine building courses every day. I think everyone before me has linked all the available resources, happy building!
I would agree with most everyone is saying, you can build fantastic elearning without any JavaScript knowledge at all. Out of the box Storyline gives you a lot of great tools and functionality. Once you've mastered all of those then you might start to think about adding some JavaScript.
One other note, you can start adding JavaScript code without really knowing how to write it (or even really understand it). There are resources on ELH with some great samples where all you have to do is copy the code and paste it into a trigger.
11 Replies
Hi Sam, I would say in general, most eLearning Developers don't need to use JavaScript when developing content with Articulate Storyline and Adobe Captivate.
Typically there is already enough built-in functionality within the software where you don't really need to do any additional scripting. However, have said that, if you are able to learn some JavaScript, you can definitely do some additional cool things with Storyline/Captivate.
I would say to be considered a strong eLearning Developer, really focus on using the tools to their fullest (mastering triggers, layers etc...), strenghten your Instructional Design skills and creativiity, and also your visual design skills. Once you have that down, you can learn some JavaScript as the icing on the cake :)
Hope that helps!
I would add that this is not only true of those two tools, but most other authoring options out there. Generally speaking use of javascript is for edge cases.
I would say that JS is more of an exception than the norm with Storyline. It's a nice to have, when you can use it to create some neat things, but the out-of-the-box functionality is generally all that you need ;)
Hi Troy,
As mentioned by previous posters, both products are useable out of the box without having to have any knowledge of JavaScript at all.
To really shine at eLearning (imho), the key is to ensure that your instructional design is solid first. A module with 100 bells and whistles is of little value if it doesn't produce the result the client wants it to.
Consult with your client, storyboard your design ideas with them, and then when you know what you need to produce, use the eLearning tools to do so.
Sometimes the simplest modules produce startlingly effective results.
We used Captivate for years at my prior org. Only 2 of 7 IDs could really work with it. We switched to Storyline and the team was more productive month 1 than years with Captivate. It is easy for folks to build interactives. Folks more deeply skilled can toss in JavaScript for extras.
I have to agree with the others JavaScript is nice to have, but not needed for most things. Storyline is user friendly and has a lot of built in triggers and such. Solid understanding of adult learning and design are important. Also, remember that keeping it simple is often a great approach meaning your modules should be consistent and clear for the user. Solid understanding of these things along with resources like elearning heros and their challenges are a great way to build a solid understanding of the tools in storyline
Hi Sam, I don't know about Captivate but the Articulate Community really has some gems for starting developers. Obviously you need to start mastering your tools. So check out the Tutorials section to learn what you can do with Storyline. After that you should check out the weekly challenges. These are great mini-projects you can work on that help you put in the time needed to get really comfortable with Storyline without the stress of project deadlines and such. A save environment to mess up and learn!
Storyline has less of a learning curve than captivate, but is powerful enough to grow with your needs. You can build great courses without the need for javascript. Look at the tutorials on this site and get started.
I tend to avoid using Javascipt due to the issues it can introduce.
I've yet to find something totally impossible with the tools Storyline offers. Lynda is a great resource.
Personally, I found it easier to learn development and the structure without using templates, but perhaps that is just me.
Here is a resource that may help:
https://community.articulate.com/articles/javascript-and-articulate-storyline/
We rarely use JavaScript and get on just fine building courses every day. I think everyone before me has linked all the available resources, happy building!
I would agree with most everyone is saying, you can build fantastic elearning without any JavaScript knowledge at all. Out of the box Storyline gives you a lot of great tools and functionality. Once you've mastered all of those then you might start to think about adding some JavaScript.
One other note, you can start adding JavaScript code without really knowing how to write it (or even really understand it). There are resources on ELH with some great samples where all you have to do is copy the code and paste it into a trigger.
This discussion is closed. You can start a new discussion or contact Articulate Support.