Is it possible to hide some slides from the published output?

Dec 08, 2012

I have some slides setup which I would like to hide from the published output. Is it possible to do so and ensure that the Next and Prev buttons just skip over these slides?

Thanks for your help.

14 Replies
Rahul Paul

Hi Geert,

Thanks for your reply. I am new to Storyline so just bear with me.

If I move slides to a scene, then how do I prevent the Next button from ultimately reaching slides in that scene. Doesn't the built in player navigation just loop through all the slides in a Story?

Thanks again for your help.

With best wishes,

Paul

Geert De Rycke

Hi Paul,

I see your point, and it is a logical question, yet there's nothing to worry about. SL is smart enough to only do what you tell it to do.

If you do not want a slide to be rendered, then you should go to the slide that calls it and simply remove the trigger that calls it.

Now this is all nicely said, but what if the object that calls my slide is the next button I hear you say. Well, by moving it into an otther scene, the next trigger will not call he slide you moved, but will call the after that one.

Here's a little example

  1. Create a scene
  2. select the slides you want to move&  Cut the slidesyou want to move

  3. Paste the slide
  4. here you can see that you slide will not be called, as there are no links made to it

This technique is often used for lightbox slides. These slides are not part of a normal scenario, but are used as popup slides. Therefore it is a good practice to put them into a separate scene.

Hope it clarifies

cheers

Geert

cheers

Geert

Bruce Graham

Hi Rahul,

For what you are trying (I think...) to achieve, Geert's method is exactly the way to go.

I include a "Production Notes" section in many of the courses I create, and deploy in this way.

When I eventually hand over the files to a client, it is an ideal place to hold, for example, any instructions, explanations of recording environment, the decay settings I used on an echo - for example. Use a Scene as a "Read Me" file for anyone who will use the base .story file in the future.

Jon's method is more for slides that you DO want to include in the course, but not necessarily have people see, such as "secret" slides that appear once certain conditions are reached, or Quizzing slides that you do not want to show.

In Storyline the navigation can pretty much be set up to include, or exclude anything you want to, in any order.

Bruce

Geert De Rycke

Rahul,

in addition to what Bruce is writing, there isnothing more variable then a user/client that has not made up his/her mind (yet)

Before the actual hand over, I NEVER delete any slides, I keep them aside, just in case the user back tracks and wants me to put it as it was 3 weeks ago, you know the feeling right?

You may be able to charge him for this, but you don't have to redevelop it; It'll save you a lot of stress

Cheers

Geert

Bruce Graham

Geert De Rycke said:

Rahul,

in addition to what Bruce is writing, there isnothing more variable then a user/client that has not made up his/her mind (yet)

Before the actual hand over, I NEVER delete any slides, I keep them aside, just in case the user back tracks and wants me to put it as it was 3 weeks ago, you know the feeling right?

You may be able to charge him for this, but you don't have to redevelop it; It'll save you a lot of stress

Cheers

Geert


Agree completely

If I delete or add a slide, the course gets a new version, and all versions are kept until sign-off and invoicing!

Bruce

Rahul Paul

Thank you Geert, Bruce and Jon for your replies. 

I am able to see right away the point about having a separate scene for skides intended to be hidden from the regular navigation structure. Will experiment with the approach suggested by Jon to understand its implications. 

Thanks once again to you all for your help. The biggest plus point of Storyline that i am now getting to see is the tremendous community support available for it. 

Paul

Kelly Phillips

Hi

I've followed the instructions above, and I can get it to work.

However, because I want to track user completion, Storyline thinks there are 2 slides that need completing before a user has completed the course, as opposed to just the one 'used' slide.

Any help with this would be great!

Thanks

Ashley Terwilliger-Pollard

Hi Kelly,

If you've included extra slides that will be hidden for the user, you'd need to include one less within your track by slides viewed. So instead of tracking that they saw 2 out of 2 slides - you'd want to track that they saw 1 out of 2 slides. 

If you're still having difficulty this thread is a bit older, so it would help if you're able to share more specifics here with us on your particular set up and slides used. Also, letting us know if you're using Storyline 1 or Storyline 2 would be helpful. Lastly, I'd assume that since you're talking about tracking/completion you've uploaded this to an LMS? Could you share which other publish setting your using (SCORM 1.2, 2004, Tin Can, etc.) and what LMS you've uploaded it too?

Kelly Phillips

Hi

Thanks for that, I will give it a try.  I'm sure that will solve the problem.

I'm using Storyline 2 and am uploading the course to Litmos LMS.  I've found that using SCORM 2004 4th Edition to be giving me the best results with regards to completion percentages etc, but it's still an area I have very limited knowledge on.  I have no clue about Tin Can, tried it once and couldn't get it to work, so I gave up.

I'm still very new to Storyline and e-Learning so am stumbling my way through it all.

Web Services

On a related topic, can slides be removed from being tracked? I'm packaging up my Articulate to be run in Moodle. I want students to complete the SCORM package by getting to the last slide. Within the module I have a few different branches which means students won't always visit every single slide. At the moment Moodle reports that they have not completed. So either can I exclude slides from being tracked or can I set a 'ModuleComplete' variable on the last slide?

This discussion is closed. You can start a new discussion or contact Articulate Support.