There weren’t a lot of contributions to this area. Before we leave it for the final competency area, please check the list below to see if you would like to revise the list. Contributing participants, please check to see that changes I’ve made still reflect your intention. Remember, these are tasks that Developers, not IDs, do:
• Create and iterate on screen designs for eLearning courses
• Create graphics and media, including images, video, and audio
• Recreate diagrams and graphics that we may not have legal access to accurately, but uniquely
• Determine the best position and placement of screen elements on a page-to-page basis
• Scope the authoring and graphic elements of proposed projects
• Estimate development hours for pro formas
• Plan videos
• Determine the best way to present content
• Work around authoring tool limitations to achieve instructional goals
Hi Brisho,
Thanks so much for your comments. When we do the next area on technical skills, could you please think about the various software types (e.g., authoring, illustration, video production and editing, 3D, rendering, and tons of other stuff that I have no idea of)? Then we can add a task such as “Use SL 360, Captivate, and other industry-standard course authoring tools fluently to create online courses”. If this proves too difficult, we can add an “appendix” of skills and attributes for eLearning devs that can include required software mastery.
Creative duties are hard to summarize. There’s a lot of overlap with the technical and software specific tools.
Should we add a list of programs we are expected to work with fluently?
Adobe CC: Photoshop, Illustrator, After Effects, Animate…
Storyline 360
Captivate