With Smart Templates, you can create reusable templates that are accessible directly when you create a storyboard. Templates can themselves have associated storyboards and settings, which means that you can create highly efficient workflows.
The templates that you have defined (more on that below) are accessible directly from the Add Storyboard modal, from any job within the client that has these templates.
Furthermore – we now allow you to take a template job and "Set as Module," which enables you to create and control storyboards that you use for the Quick Insert functionality. These two features combined make for a unique workflow that gives you massive speed and efficiency.
Template Job: A job that holds one or more storyboards that are meant to be used either as a template or as modules.
Template: A storyboard within a template job that acts as a template for new storyboards anywhere within a client. So when creating a new storyboard from any campaign, you have access to your templates. Using a template creates a new storyboard with the exact same settings and contents as the template. When updating a template, any subsequent use of that template will reflect the update.
Module: A storyboard that is associated with a template by the use of the Quick Insert functionality. These storyboards can also reside within a template job, which is "Set as Module," which means these storyboards are not used as templates but have a place within the Templates & Modules tab.
What is a Template?
A template is a storyboard, with all its settings, slides, used assets, slide notes, slide intentions, and associated storyboards (Quick Insert Modules) that you add to your client in one of the ways outlined below.
In Storykit, we have created a particular class of jobs that are made for holding templates, which makes it easy and safe to manage both templates and storyboards you are using for the Quick Insert function.
What is a Module?
A module is also a storyboard – but made for inserting into other storyboards, as modules that allow you to build up your complete movie with "lego-like" pieces. These modules are associated with one or more templates and are accessible within the template storyboards to give you quick access to these pre-made parts of the movie.
The point of using modules is that often a template itself is "too much and too little" at the same time, not giving you enough flexibility to create what you want. And also, since you can use your modules in any number of templates, they become your bread and butter storytelling elements.
When you create a Template job and set it to module – all modules in that job with an insert access of "Within Client" or "Public" will be automatically available for Quick Insert in all storyboards within your client, which makes it a great way to create a library of re-usable parts for even faster workflow.
In practice, it can look something like this.
You have a template for a story format called "Listicle Template." This template is a storyboard with an intro and a couple of explanatory slides because you have decided that this story format needs that.
Then you want to have an unknown number of listicle points or segments. So these are made as modules ("Listicle Segment") that are associated with the Listicle template. So within the storyboard that you create from the Listicle template, you can insert the "Listicle Segments" one at the time.
How do you create a template?
In your client settings, you have "Template & Modules," which gives you access to a specific type of job that "only" holds storyboards that will serve as templates for new storyboards.
One template job can hold multiple template storyboards, and they are sorted under the job name when you invoke the template list – so think of each template job as a folder of templates of a specific type.
Controlling the visibility of templates
The visibility for a template is determined by the storyboard "Insert Access." This means that even if you have a lot of storyboards in the same job, only the ones with the correct insert access will be visible for other users. So a storyboard must have at least "Within Account" to be usable as a template. And if you plan on letting users outside your organization use your templates, you can set them to "Public" and let those users add these jobs as Additional Templates.
How do you add templates from other sources – Additional Templates?
Apart from the templates that are present within the Template Jobs, you can also add templates from other jobs – even globally accessible ones. To add a template that is outside your own Template jobs, you add the ID of that job (copy the ID with the "Copy ID" function in the template job list) in the "Additional Templates" field in the "Client Settings." You can add as many ids as you like, as long as they are comma-separated.
When adding an id to a Template Job, the same rules apply: So only the storyboards that have the correct Insert Access will end up in your list of Templates. So when sharing templates outside your account, those storyboards must have "Public" Insert Access. But as you'll quickly realize, this means that you can have both internal and external templates in the same template job, which makes the workflow between them a lot simpler.
Using a template
Whenever you create a new storyboard from anywhere within your client, you now have access to your templates. So you can start with a "blank" storyboard or with a template.
Choosing a template will de-activate the format settings in the Add Storyboard modal, and create the new storyboard with the format that you built you used for your template. If you want to change this, you can do so in the storyboard later.