add custom content to 'index.html' to be included in build

[blakestonex]

Hello,

I have been asked to use the Adobe Captivate to test a number of features which include linking this with some external web content such as linking with AngularJS, Bootstrap, MongoDB etc. For a lot of this to work I need to add a heap of data to the index.html file - I can obviously do a build and then edit the index.html this way however is there a way to add all of this content prior to the build so that we can click 'build' and it's all ready to go?

Thanks,

[blakestonex]

I have found that I can modify the template file - which in my case is 'standard.htm' and this works.

Can I add these changes via the editor so that I am not editing the template file? or can I copy 'standard.htm' and name this 'standard_projectX.htm' and select to use this for the project / build?

Thanks,

[TLCMediaDesign]

You'll need to make a copy of the standard.htm, name it standard_original.htm.

Then copy the standard_projectX.htm and name it standard.htm.

You'll need to manually change them when you work an a different project.

[blakestonex]

I thought this might be the case - thanks.

[RodWard]

If you are publishing to SCORM there may be an alternative.

The SCORM settings panel has a dropdown field called Template which allows you to select from a number of options for where Captivate gets the files it uses in your output.

If you dig down into the Captivate Program Files structure you can find these three options as folders.

If you take a look inside the Default folder you can see how Captivate will be selecting files for SCORM 1.2 or 2004 and where it will get the JS files.  In the case of the SendTrackingDataAtEnd folder, there’s only a JS folder, so it seems to be coded to ONLY substitute default files with ones that it finds in the folder you select.

Now if you create another folder in this group, say one called MyProject, when you relaunch Captivate you will see that folder available from the list.

This gives you the ability to have any number of folders (but only one level of them) available from this list and in those folders you can put your own customized SCORM code files.  I have used this technique in the past for clients that had to have customized templates. I could put a folder in this location for each one.

You need to test all of this out with HTML5 to make sure that HTML5 output still uses all of the same code and the files from these locations.  But this might be a possible way you could have customized templates or SCORM JS code for projects that get served up from an LMS.

[TLCMediaDesign]

I'm going to test this in html5 Rod, thanks.

[Michael Spain]

Rod,

Is there perhaps another step in the process? When we move a custom folder in, we do see the folder name as a "Template" option.

And when we select it, we see that it is the selected option.

But when we publish, we see only the data from the Default folder. We confirmed this by updating the imsmanifest under the Default folder with a comment. When we publish using our custom option, we see the comment from the Default folder imsmanifest version.

Is it possible we have missed a step?

Thank you,

Michael

[RodWard]

Not necessarily that you missed a step.  It's more likely that Adobe has dropped the ability to customise your SCORM templates this way.  Perhaps now that mobile has arrived it has introduced too much complexity.  I haven't used this method in years now, so I haven't been checking with each new version to see if the functionality still exists.