The Captivate themes you are using as a developer are stored in the Public Documents (Windows, for Mac under Shared), in the subfolder ‘Layouts’ of the ‘eLearning Assets’, at the same level as the Theme Colors palettes. They show up as thumbnails when you click on the Big Button ‘Themes’. You can use them for normal projects as well. Since Captivate 8 most of those themes are responsive. Each Captivate version since 6 ships with several themes. You can have themes for a normal (blank) or for a responsive theme. Applying a well designed theme to a project,should change the ‘look’ immediately it will not take a lot of editing later on.Ī theme is saved in a file with extension cptm. Although most themes will be created for a certain resolution (size in pixels), when they are designed correctly you can also apply them to projects with another resolution. A theme can be ‘applied’ to any project, even after creation, as long as it is a project of the same type, normal or responsive. The goal of a Captivate theme is to have a consistent design throughout your project’s). This article will explain my use of custom Themes, and the reason why Templates have lost significance as design tool when Themes appeared with version 6.
My blog fans know that I like to talk about the “hidden gems”, which can help saving time and frustration. These improvements have not been emphasized as much as the more ‘hype’ features. Captivate has evolved a lot (since I started using version 1), also in its design tools. Similar confusion can be found in many training schedules and books. Whether I work with clients or answer questions on forums/social media, I often bump onto confusion between themes and templates.