Skip to main content
Consistent docs come from two levers: templates, which define the shape a new doc starts from, and style, which defines the voice everything is written in. Both live in Settings, and both apply to human authors and AI generation alike.

​
Templates

Open Settings → Templates to manage your organization’s doc templates. A template is a starting point for a new doc, with:
  • A name and description so authors know when to use it.
  • A body — the headings and boilerplate a new doc begins with.
  • Optionally, a gold-standard exemplar — a finished doc that shows what “great” looks like for this type.

​
Built-in starters

Fifteen built-in starters cover the common Salesforce documentation shapes, grouped in two families:
For business audiences — process guides, user FAQs, business glossaries, onboarding guides. These explain what the org does in the language of the people who use it.
For builders — technical references, integration docs, data dictionaries, runbooks, troubleshooting guides. These explain how things work and what to do when they don’t.
You can use starters as-is, or save your own templates tailored to your team’s conventions.

​
Exemplars teach the AI

An exemplar is more than an example for humans. When a template carries one, the AI uses it as a few-shot example during generation — matching its depth, structure, and tone. If your best runbook sets the exemplar, generated runbooks aim for that bar.
Pick your single best doc of each type and attach it as the exemplar. One genuinely good example moves generation quality more than a page of written instructions.

​
Where templates apply

The New page dialog in the docs viewer offers three choices: Plain (empty page), a built-in starter, or one of your saved templates. Pick one, name the page, optionally link it to Salesforce metadata, and start writing.

​
Style

Open Settings → Style to define how your docs sound.
1

Pick a built-in preset

Choose a recognized style baseline — for example, Google developer style or Write the Docs.
2

Add organization overrides

Layer your own rules on top: terminology (“say ‘customer’, never ‘client’”), formatting conventions, tone adjustments, things to avoid.
3

LivingContext composes the effective style

The preset plus your overrides form a single effective style, applied to every generation.
The effective style applies everywhere docs are generated — Inbox proposals, Commits drafts, and Doc Editor Agent edits — so agent output reads like your team wrote it.
Style guides generation; it doesn’t rewrite existing pages retroactively. Existing docs pick up the style as they are next updated through the normal flows.

​
Putting both to work

Start with the built-in starters and a preset, then tighten with saved templates, exemplars, and overrides as your team’s preferences become clear.