This page covers templates: designs you save by name, apply to a whole list, and reuse next week.
Which designers you have
Saving a design under a name, choosing a default for a list, applying one to everything at once, and the designer window itself work the same for every kind of item. What you make with it is yours.
Which designers you have depends on which modules are switched on. If a colleague has a designer you do not, look under Settings → Modules, not for a setting.
How templates work
A template is a saved set of design choices with a name.
| Level | What it means |
|---|---|
| A default for the list | Everything of that kind in this rundown uses it |
| A template on one item | That item overrides the default |
| Apply to the whole list | Push one template over everything at once |
The order is the useful part: set a default once, override the exceptions, and a rundown built from a hundred items needs one decision plus a handful.
Where designs come from
Two sources, and they behave differently:
Yours. Made in the designer, saved by name, stored with the program. You can change them whenever you like and they follow your house style.
A publisher’s. Content a module fetches from an external source can bring its own design with it, so it appears the way its publisher intended without anybody setting anything up.
Practical notes
Name templates after what they are for, not after what they look like: Sunday morning, not Blue large. Six months later the first one still means something.
One default well chosen beats twenty templates. Every extra template is another thing that can be applied by mistake.
Templates live with the program, not with the list. A rundown opened on another machine finds that machine’s templates. If a show has to travel, check that its designs travelled too.
Where to read further
Which fields, effects and options each designer holds is in the part of this manual for the module that supplies it.