ElfVengers Support Docs¶
TL;DR
The internal operational handbook for the ElfVengers — ElfHosted's support team. Everything you need to triage tickets, troubleshoot apps, and run common support tasks lives here. Start with ElfVenger onboarding.
This site is internal and access-gated — it is not the public ElfHosted docs. It holds the operational knowledge a support agent needs: how things actually work, who to escalate to, and the step-by-step runbooks for the tasks that come up in the queue.
How this is organised¶
| Section | What's in it |
|---|---|
| Getting started | Onboarding a new ElfVenger — accounts, tools, how we work. |
| Runbooks | Task-oriented, step-by-step procedures ("how do I do X"). |
| Reference | Lookups — tools, systems, links, glossary. |
| Support process | When to escalate issues and how front-line support hands off tickets. |
| Glossary | ElfHosted / support terms and acronyms. |
Using these docs¶
- Skim the TL;DR first. Every page leads with an actionable summary — under queue pressure, that block alone should answer the question.
- Search is your friend (top bar). The nav is curated; not every page is linked.
- Found something wrong or missing? Fix it — see Contributing below. These docs are only useful if the team keeps them honest.
Contributing¶
This repo is built and maintained with Claude Code.
If you're here to add or import docs, open the repo in Claude Code and read
CLAUDE.md — it will walk you through the workflow (and, on a fresh/empty repo, run a
short onboarding interview to set up the structure). The short version:
- Copy
_page-template.mdinto the right section underdocs/. - Write it (see how to write a runbook for the house style).
- Preview with
scripts/serve.sh, thenscripts/build.sh(must be 0 failures). - Land it via a PR with a Conventional Commit
title —
feat:for new pages,fix:for corrections. That drives the changelog and release automatically.