# Help center article templates

From the Clevera guide "How to write help center articles": https://www.clevera.ai/blog/how-to-write-help-center-articles
Copy a template, replace everything in [brackets], and delete any section you don't need.

---

## Template 1: How-to article

# [Verb] [the thing] (example: Invite a teammate to your workspace)

[One or two sentences: what this does and the result. Answer the question here, so someone who reads only this paragraph knows what to do.]

**Before you start**
- You need: [plan, role or permission]
- Have ready: [file, account, information]

**Steps**

1. Open **[exact menu or page name]**.
2. Click **[exact button label]**.
   [Screenshot of the screen just before the click, with the button marked]
3. [Enter / choose] [what], then click **[button]**.
4. [Last action]. **You'll see:** [what tells the reader it worked]

**If it doesn't work**
- **[Symptom in the reader's words]:** [cause in one line]. [Fix.]
- **[Symptom]:** [Fix.]

**Related**
- [Next task people usually do] ([link])
- [Concept they may need] ([link])

Last updated: [date] · Owner: [name or team]

---

## Template 2: Troubleshooting article

# [Symptom in the reader's words] (example: Invitation email didn't arrive)

[One sentence: the most common cause and its fix.]

**Check these first**
1. [Quickest check]. [What to do if that's it.]
2. [Next check]. [Fix.]
3. [Next check]. [Fix.]

**Still not working?**
[What to send support so they can help fast: screenshot, account email, time it happened.] [Contact link]

Last updated: [date] · Owner: [name or team]

---

## Template 3: Concept article (what is X?)

# What is [feature or term]?

[Feature] is [one-sentence definition]. [Why it matters to the reader in one sentence.]

**How it works**
[Two or three short paragraphs or a short list.]

**When to use it**
- Use it when [situation].
- Don't use it when [situation]; use [alternative] instead.

**Next steps**
- [How-to article that puts it to use] ([link])

Last updated: [date] · Owner: [name or team]

---

## Before you publish: checklist

- [ ] The title is a task or question, in the words customers use
- [ ] The first paragraph answers it
- [ ] Every UI label is in bold and matches the product exactly
- [ ] One action per numbered step; 3 to 12 steps
- [ ] Screenshots show the screen before the click, with the target marked, and no real customer data
- [ ] Prerequisites and the expected result are stated
- [ ] Someone who didn't write it followed it without help
- [ ] It links to the next task and is listed in the right section