Page template

Every topic page follows this template, so that competitors find the same things in the same place on every page. Copy it into a new .md file under src/content/docs/, give it a title in the front matter, and fill in each section.

A few conventions:

• Anchors: put {#anchor-name} after H2 and H3 headings. Roadmaps deep-link to them, so keep them stable once published.
• Callouts: use Starlight asides: :::note, :::tip, :::caution or :::danger, with an optional [Title].
• Tags: list the competition module, the WSOS section(s), topic keywords and a category. They feed the tag index.
• Review date: add reviewed: YYYY-MM-DD when the page has been checked against the latest WorldSkills International and WorldSkills UK documents.

---
tags:
  - area-offensive-operations   # or area-infrastructure-hardening / area-digital-forensics / area-defensive-operations
  - wsos-6-operations-management   # the main WSOS 2026 section this page supports
  - wsos-7-intelligence   # add secondary WSOS sections as relevant
  - topic-keyword   # e.g., linux, hardening, xss, forensics, etc.
  - category   # e.g., offensive, defensive, forensics
---

# Topic Title

---

## Scope

**What this is:** One-sentence description of the topic.

**Competition relevance:** Which competition area(s) this serves, and from which stage (regional/national/squad/international). Do not quote mark percentages: WorldSkills does not publish module weights.

**Why it matters:** Brief explanation of why this skill is valuable in competition context.

**WSOS 2026 alignment:** This topic directly supports **Section [X]: [Section Name]** (brief explanation of how this topic demonstrates that WSOS competency).

**Competition area:** Core to the **[infrastructure hardening / digital forensics / offensive operations / defensive operations]** area, where you [brief explanation of how this topic fits into that area's tasks].

**Offline competence:** How to perform this task with limited or no internet. Mention specific offline resources: man pages, `/usr/share/doc`, Zeal docsets, Kiwix offline Wikipedia, built-in tool help (`--help`, `-h`), local wordlists, pre-downloaded tools, browser DevTools, etc. Be specific about what works offline and what doesn't.

---

## Competency Matrix

| Level | Expectation |
|-------|-------------|
| **Regional** | Basic skills expected at regional level. |
| **National** | Intermediate skills for national competition. |
| **Squad/Team Selection** | Advanced skills for squad selection. |
| **International** | Expert-level skills for international competition. |

---

## Technical Content

### Subtopic 1 {#anchor-name}

**What it is:** Brief explanation.

**Example:**
```bash
# Example command or code
command --option value
```

**Output:**
```
Expected output
```

**Competition context:** How this appears in competition scenarios. What to look for.

---

### Subtopic 2 {#another-anchor}

**Key concepts:**
- Point 1
- Point 2
- Point 3

**Example vulnerability or technique:**
```language
code example here
```

**Exploitation steps:**
1. Step one
2. Step two
3. Step three

---

## Competition Strategy & Marking

**What gets marked:**
- Specific artefact 1 identified/exploited/remediated
- Specific artefact 2 with context (command output, screenshot, file hash, etc.)
- Specific artefact 3 with written explanation
- Documentation quality and clarity

**Evidence and reporting requirements:**
- Screenshots must show: [specific UI elements, command output, hostname, timestamp, username visible]
- Command history or tool output proving method used
- File hashes (MD5/SHA1) for any extracted files or malware samples
- Written explanation of findings with technical detail (e.g., "Process svchost.exe running from C:\Temp is suspicious because...")
- Timeline of events if applicable (ISO 8601 format or UTC preferred)
- Before/after comparison for remediation tasks
- Clear file naming convention: `[topic]_[hostname]_[artefact].png` or `.txt`
  - Examples: `xss_webserver_reflected_payload.png`, `forensics_host1_registry_autorun.txt`

**Time allocation:**
- Task 1: [X] minutes
- Task 2: [X] minutes
- Task 3: [X] minutes
- Total: [X] minutes

**Time-boxed drill suggestion:** [X]-minute [topic] sprint: Given [scenario], [perform specific task 1], [perform specific task 2], [achieve specific outcome], and document all findings with [specific evidence types]. This drill should be completable offline using [specific tools/resources].

---

## False Flags / Wrong Paths

:::caution[Common Traps]
**Trap 1 title**
Description of common mistake and why it happens.

**Trap 2 title**
Another pitfall to avoid in competition.

**Time sink warning**
Don't waste time on [specific activity]. Focus on [alternative approach].
:::
---

## Practice Checklist

- [ ] Can perform [specific skill 1] without documentation
- [ ] Can identify [specific artefact or vulnerability type]
- [ ] Can exploit/analyse [specific technique]
- [ ] Can document findings with proper evidence format
- [ ] Understand [key concept or tool limitation]
- [ ] Can complete [realistic task scenario] in under [X] minutes without internet access

---

## References

**Primary references:**
- [WSOS 2026](/wsos/), Section [X]: [Section Name] ([brief reason why this section is relevant])
- Competition stage roadmap: See ../00-roadmaps/ for appropriate stage (regional/national/squad-selection/international)

**Related topics in this knowledge base:**
- Cross-reference related topics with proper relative paths based on file location

**Cheat sheets and quick references:**
- Link to relevant cheat sheets in ../99-cheat-sheets/ when available

**External resources (for offline preparation):**
- Tool documentation: `man [tool]` or `/usr/share/doc/[package]`
- Offline documentation: [specific Zeal docset, Kiwix content, or downloaded resource]

---

## Notes for Template Usage

**This template section should be removed when creating actual topic pages.**

### Key principles:
1. **British spelling throughout**: analyse, defence, artefacts, unauthorised, organisation
2. **No "Day X" language**: Use "module" and "competition stage" instead
3. **Anchor IDs**: Use {#anchor-name} for all H2/H3 headings for stable deep linking
4. **Tags**: Front matter tags should include module (a/b/c/d), WSOS section(s), and topic keywords
5. **Word count**: Aim for 600-1200 words of substantive content
6. **Offline-first mindset**: Always specify what works offline and what doesn't
7. **Evidence-focused**: Competition marking depends on evidence quality, so be explicit about requirements
8. **Time-boxing**: Include realistic time estimates and practical drill suggestions

### Front matter tags reference:

**Competition area tags** (choose 1-2):
- `area-infrastructure-hardening` - Infrastructure hardening and secure coding
- `area-digital-forensics` - Digital forensics and incident response
- `area-offensive-operations` - Offensive operations (red team CTF)
- `area-defensive-operations` - Defensive operations (blue team)

**WSOS 2026 section tags** (choose 1-3; see [WSOS 2026 sections](/wsos/)):
- `wsos-1-work-organisation` - Section 1: Work organisation and management (5%)
- `wsos-2-communication` - Section 2: Communication and interpersonal skills (10%)
- `wsos-3-secure-design` - Section 3: Secure systems design and creation (10%)
- `wsos-4-operation-maintenance` - Section 4: Secure systems operation and maintenance (15%)
- `wsos-5-protection-defence` - Section 5: Secure systems protection and defence (15%)
- `wsos-6-operations-management` - Section 6: Operations and management (20%)
- `wsos-7-intelligence` - Section 7: Intelligence collection and analysis (10%)
- `wsos-8-investigation-forensics` - Section 8: Investigation and digital forensics (15%)

**Category tags** (add as relevant):
- `offensive`, `defensive`, `forensics`, `infrastructure`, `web-security`

**Topic-specific tags** (add as relevant):
- Tool names: `nmap`, `wireshark`, `volatility`, `burp-suite`
- Techniques: `xss`, `sqli`, `privilege-escalation`, `log-analysis`
- Platforms: `linux`, `windows`, `active-directory`, `web`

### Relative path patterns:

**For files at 1-level depth** (e.g., `docs/01-category/file.md`):
- Roadmaps: `../00-roadmaps/[stage].md`
- Cheat sheets: `../99-cheat-sheets/[topic].md`
- Other categories: `../02-category/[topic].md`

**For files at 2-level depth** (e.g., `docs/03-category/subcategory/file.md`):
- Roadmaps: `../../00-roadmaps/[stage].md`
- Cheat sheets: `../../99-cheat-sheets/[topic].md`
- Same category: `../other-subcategory/[topic].md`
- Other categories: `../../02-category/[topic].md`