Reusable Snippets: Write the Refund Policy Once
Knowledge now supports reusable snippets you write once and reference across as many pages as you need.
If your docs site has a refund policy, a support-hours notice, or a legal disclaimer that shows up on more than one page, you've probably run into the same problem every documentation team eventually hits: you wrote it once, then copied it, and now updating it means finding every copy and hoping you didn't miss one. Knowledge now has a real answer to that — reusable snippets.
How it works
You write a snippet once, give it a key, and drop a reference to that key — ::snippet{key} — into any page where you want that content to appear. When the snippet's content changes, every page referencing it updates automatically, because there's only ever one copy of the text, not many.
Saving a snippet is deliberately forgiving: if you save under a key that already exists, it updates the existing snippet in place rather than erroring out or creating a duplicate. You don't have to remember whether you're creating something new or editing something old — the system figures that out from the key.
Consistent everywhere it's used
Snippets resolve the same way whether you're looking at a live preview while editing or at the page your readers actually see once it's published. There's no separate "preview version" and "published version" of a snippet's content to keep in sync — it's the same resolution logic in both places.
Where to start
If you maintain any boilerplate text across multiple pages — a policy, a standard warning, a repeated call-to-action — that's the first candidate to turn into a snippet. Find it in the Knowledge editor's content tools, and reference it by key anywhere you need it.