Skip to main content
Inspiring
April 11, 2016
Question

How to share the same content throughout a project?

  • April 11, 2016
  • 2 replies
  • 393 views

I am building a project that will allow the user to display information from many places. For example, common instructions, an "About" screen, the course objectives, and course credit info.

What is the best way to build that content once so that it can be displayed at any time in the project?

For example, should the buttons to show this content call javascript to open a another web page? Or is it possible to show a slide from another project in a modal window, that contains this common data?

This topic has been closed for replies.

2 replies

BDuckWorks
Inspiring
April 11, 2016

"common instructions, an "About" screen, the course objectives, and course credit info."

It sounds like each of your examples could be an object on the first slide, set to be displayed for the rest  of the project, but hidden upon publish, then revealed by a show/hide toggle button.

As RodWard mentioned, Capivate isn't really designed for content re-use, but this kind of hide/show interaction is pretty common.

I'd suggest you search these forums for references to a 'toggle button.'

RodWard
Community Expert
Community Expert
April 11, 2016

A Captivate project published to HTM/SWF or HTML5 and deployed from a website certainly CAN call a web page.  However, if your project is intended to be deployed as a SCORM course tracked by an LMS then calling web pages or files OUTSIDE the SCORM object is forbidden by the SCORM standard, as each individual SCO module is supposed to be standalone.

I appreciated your intention is to reuse the content from a single location, and ironically, the rule in the SCORM standard was originally trying to preserve the reusability of SCOs, but some good intentions just seem to work against each other.

Pete47Author
Inspiring
April 11, 2016

Fortunately, this project isn't a SCORM object so I could use a web page approach.

Is that our only option in a situation like this?

Another thought might be to navigate to and from the target page with the desired information. But that would mean I won't have the "overlay" effect because it would be a complete jump to another slide and back.

But back to the web page approach, I am wondering if I can use a relative link to the desired page rather than a hard coded page... but that would require everything is bundled together into one package. Is there anyway to instruct Captivate to include other resources when it packages everything; guessing not since this isn't a SCORM package file I'd be creating.

RodWard
Community Expert
Community Expert
April 11, 2016

Captivate is more designed for people that are looking for something that comes pre-packaged with all the components it needs to work right out of the gate.  It's not designed specifically to easily support reuse of components between modules.