If the same paragraph lives in five places, it will eventually say five different things. Single-sourcing means you write content once and reuse it wherever it's needed.
Why reuse
- Accuracy: fix a mistake once and it's fixed everywhere.
- Speed: new guides are assembled from existing, reviewed blocks.
- Consistency: the same warning always has the same wording.
- Lower translation cost: repeated text is translated once.
The three building blocks
🔤 Variables — for values that change: product name, version, support email. Update the variable and every topic updates.
🧩 Snippets — for reusable chunks: standard notes, warnings, prerequisites, legal text. Edit the snippet once; every topic that includes it changes.
🎯 Conditional content — for audience or product differences: one source topic, with parts shown only for admins, a specific edition, or a specific output (web vs PDF).
Try it: variable, snippet, or condition?
The product name will change from "Acme Docs" to "Acme Knowledge" next quarter.
✅ Variable. Insert the name as a variable everywhere; the rename is a one-line change.
The same "Back up your data before you upgrade" warning appears in 14 topics.
✅ Snippet. One reviewed warning, included in all 14 topics.
Admins need two extra steps that regular users must not see.
✅ Conditional content. Mark the admin steps with a condition and publish separate outputs for admins and users.
Common mistake: over-reusing
Don't turn every sentence into a snippet. Reuse blocks that are genuinely identical and stable. If a "reusable" block needs editing in every place it appears, it isn't reusable — write it in context.
âž¡ Next: Write for accessibility and translation