Start with structure, then replace every placeholder with information that is true, relevant, and natural for your context. These templates are intentionally skeletal so your final writing does not sound mass-produced.
A strong help article matches one clear user intent, states prerequisites, gives ordered steps, explains expected results, anticipates common failure points, and links to the next relevant task without burying the answer in background.
Title: [Verb + object/task] Quick answer: [one-sentence outcome] Before you begin: [prerequisites] Steps: 1. [Action] 2. [Action] 3. [Action] Expected result: [confirmation] Troubleshooting: [common issue] Related: [next task].
Problem article: Symptom | Likely cause | Fix | Verify | If it still fails.
How-to step: [Imperative verb] [exact UI object]. [Short result/context if needed].
Permission note: You need [role/permission] to [task]. If you do not have it, contact [appropriate owner/process].
Persistent editorial registry audit: Topic slug → [ ]; claim UID/key → [ ]; source UID/key → [ ]; dependency UID + strength → [ ]; source status/version → [ ]; open review UID/reason/priority → [ ]; replacement source if any → [ ]; reviewer + resolution → [ ].