# Getting Started Template

> **Use this template** for user onboarding guides. More detailed than QUICK-START — includes training/testing sections.

---

## When to Use

| Guide Type | Use Case |
|------------|----------|
| **QUICK-START** | Experienced users, fast setup |
| **GETTING-STARTED** | New users, training, testing workflows |
| **README** | Project overview, not onboarding |

---

## Template

````markdown
# Getting Started with [Project Name]

> **Goal:** Get you productive in 10 minutes with hands-on practice.

---

## Prerequisites

**Required:**
- [ ] [Tool 1] installed (`command --version` to check)
- [ ] [Tool 2] installed
- [ ] Access to [resource]

**Optional:**
- [ ] [Nice-to-have tool]

**Check everything:**
```bash
# Run this to verify prerequisites
[verification command]
```

---

## 1. Installation (2 min)

### Step 1.1: [First action]
```bash
[command]
```

### Step 1.2: [Second action]
```bash
[command]
```

### Verify installation:
```bash
[verification command]
# Expected output: [what they should see]
```

---

## 2. First Use (3 min)

### Try it now:
```bash
# Your first [action]
[command]
```

**What happened:** [Brief explanation of what they just did]

### Try another:
```bash
# [Second basic action]
[command]
```

---

## 3. Core Workflow (3 min)

The typical workflow is:

```
[Step 1] → [Step 2] → [Step 3] → [Result]
```

### Practice the workflow:

**Step 1:** [Action]
```bash
[command]
```

**Step 2:** [Action]
```bash
[command]
```

**Step 3:** [Action]
```bash
[command]
```

---

## 4. Test Yourself (2 min)

Complete these tasks to verify you understand the basics:

### Task 1: [Simple task]
<details>
<summary>Hint</summary>

```bash
[hint command]
```
</details>

<details>
<summary>Solution</summary>

```bash
[solution command]
```
</details>

### Task 2: [Medium task]
<details>
<summary>Hint</summary>

[hint text]
</details>

<details>
<summary>Solution</summary>

```bash
[solution command]
```
</details>

### Task 3: [Combining concepts]
<details>
<summary>Solution</summary>

```bash
[solution command]
```
</details>

---

## 5. Quick Reference

### Essential Commands

| Command | What it does |
|---------|--------------|
| `[cmd1]` | [description] |
| `[cmd2]` | [description] |
| `[cmd3]` | [description] |

### Common Patterns

```bash
# Pattern 1: [name]
[command pattern]

# Pattern 2: [name]
[command pattern]
```

---

## 6. Troubleshooting

### "[Error message 1]"
**Cause:** [why this happens]
**Fix:**
```bash
[fix command]
```

### "[Error message 2]"
**Cause:** [why this happens]
**Fix:**
```bash
[fix command]
```

### Still stuck?
- Check [documentation link]
- Run `[help command]`

---

## Next Steps

Now that you know the basics:

1. **[Next topic]** — [link to guide]
2. **[Advanced feature]** — [link to guide]
3. **[Integration]** — [link to guide]

---

## Cheat Sheet

```
┌─────────────────────────────────────┐
│  [PROJECT NAME] CHEAT SHEET         │
├─────────────────────────────────────┤
│  [cmd1]     [short description]     │
│  [cmd2]     [short description]     │
│  [cmd3]     [short description]     │
├─────────────────────────────────────┤
│  Workflow: [step] → [step] → [step] │
└─────────────────────────────────────┘
```
````

---

## ADHD Tips for This Template

1. **Time estimates** — Always include them (builds trust)
2. **Verify steps** — Every section should have a way to confirm success
3. **Collapsible hints** — Let users try before seeing answers
4. **Visual breaks** — Use horizontal rules between sections
5. **Cheat sheet** — Provide a copy-paste summary at the end
6. **Progressive complexity** — Start simple, build up

---

## Comparison with QUICK-START

| Aspect | QUICK-START | GETTING-STARTED |
|--------|-------------|-----------------|
| Length | ~1 page | 2-4 pages |
| Audience | Returning users | New users |
| Practice | None | Hands-on tasks |
| Testing | None | Self-test section |
| Troubleshooting | Minimal | Dedicated section |
| Time to complete | 30 seconds | 10 minutes |
