If e-learning is considered, we have many authoring tools at our disposal that help us easily develop the e-learning courses in no time. But, developing the training effectively is also important. Before publishing, clean up the unused/duplicate slide masters.We usually talk about the important role end-user training plays during ERP implementation. When you import slide and scenes from one story to another story file, Storyline creates duplicate slide masters even when they are exactly same. Optimize the quality of images, videos & audio using quality settings on publishing screen based on the delivery platform.
Give sufficient silence period at the between audio/video auto-play to avoid audio-video lag, audio overlapping & audio truncation. Audio/video synchronization may also become erratic.
Having multiple videos & images in the same slide (or in layers) can increase the slide loading time. If there are animations which do not require user interaction, look at the possibility of creating them as videos outside Stroyline 2 (for example power point), This will avoid complicating the slide with objects, timelines & triggers to build similar animation in Storyline. This will directly contribute to overall size of the course. If a video is used 10 times across slides, 10 copies are created. There is no concept of global repository or reuse of multimedia files across slides. This should not become an issue if you have spent good time in building & finalizing the slide masters before building modules. Any changes to master slides will have to be replicated in all the module story files. Since you are creating multiple independent modules (story files), slide & feedback masters get duplicated in each story file. When linking the modules in the global menu, use relative path (of story.html or story_html5.html) in these module folders in global menu (using external URL trigger). You can only link to starting point of a module from another module since each module is a separate published output.ĭefine your published output folder structure for the entire course with each sub-folder to keep published output of respective modules. It is important to ensure that your modules are independent & module level content is not interlinked with other module level content. When the entire course is developed as 20-25 independent modules (story files), you are essentially linking published module entry points through global menu. There are multiple advantages of this approach including parallel development of modules, easy maintenance, slicing & dicing modules to build new courses like beginner, advanced, etc of 30 to 60 minutes length, breaking -up into modules is just next logical step. If you have done good job in defining course structure into small self-sufficient sections, topics, lessons, etc. This will help apply global font changes & color scheme changes across all slides through slide master.īuild smaller modules (each module as separate story file).
Switching back & forth at later stage is almost impossible without messing up the content positions & alignments.ĭefine your theme font & color schemes at the slide master level & retain the same scheme in all the slides unless it is absolutely necessary to deviate. Master slide is not just about layouts, it is great place to define & place your global components like background colors/images, header, title bar, footer, menu bars, help, resource links, logo, fonts, etc., Ability to control these at master slide level gives lot of flexibility for course-wide changes at later stage.īefore you define master layouts, decide your slide size ratio (4:3 or 16:9). Having well-designed layouts can reduce your development time considerably & at the same bring uniformity & consistency across course modules. Instructional design & detailed storyboards become very important inputs in designing master layouts.
0 kommentar(er)
