A style template in RixSlides is your deck design, saved for reuse: the masters, layouts, fonts and colors that make ten decks look like one organization's work. You tune a design once, save it as a template, and from then on new decks — whether you build them slide by slide or generate them with AI — start from that system. Teams that use templates stop re-deciding the same decisions.
What a template contains
A style template packages the layers that define a deck's look:
- The master with its shared elements: fonts, color scheme, logo placement, footer and fields.
- The layouts beneath it: title slide, section divider, content slide, comparison, and whatever else your flow needs.
- Chart and table styling cues, so data visuals adopt the same palette as the text.
- The general canvas behavior — backdrop treatment, spacing rhythm — that the slide QC agent then audits against.
It does not contain content. A template is the stage, not the play.
Save a template from a deck you like
- Build or import a deck whose design works. Imported .pptx files bring their masters along intact, thanks to byte fidelity.
- Open MasterView and finish the system: consistent fonts, the logo on the master, a slide number field, layouts for each slide role your team uses.
- Save the design as a style template and give it a name your team will recognize.
- The template now appears in the style picker wherever decks begin.
Reuse it everywhere
From that point, the template works on both paths:
- New deck from template starts a hand-built presentation already wearing the design.
- AI deck generation with this style produces generated decks that land on-brand on the first pass — you choose the saved style in the generation flow, and the pipeline places content into your layouts rather than a generic look.
The second one is where templates pay for themselves fastest. Generated decks are only as good as the style they generate into, and a saved brand style turns "AI made a deck" into "AI made our deck."
Update the template, not forty decks
Brand changes are where templates compound:
| Change | Without a template | With a template |
|---|---|---|
| New logo | Touch every deck's master, or every slide | Update the template; new decks inherit |
| Color refresh | Re-style charts and shapes per deck | Restyle once in the template |
| New layout need | Improvise a layout in each deck | Add the layout once, reuse everywhere |
Existing decks keep their own copy of the design (byte fidelity means nothing mutates behind your back); new decks pick up the update. For an in-flight deck that needs the new look, slides transfer into a deck built on the updated template, with paste options deciding whether content adopts the new theme.
Team consistency in practice
- Agree on one template per brand level — corporate, plus maybe a product template — and resist the third variant.
- Name templates for their use, not their version: "Sales pitch" ages better than "v3 final."
- Let the slide QC agent enforce the system mechanically: it flags misalignment against the layouts the template defines.
- Keep the master sparse. Everything on it appears everywhere, so restraint scales.
What to explore next
- Masters and layouts for the layer the template packages.
- AI deck generation to put the template to work at generation time.
- Export PDF and PNG to ship decks that look the same everywhere.