> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hedwig.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Start here

> The shortest path from adding Hedwig to a useful, protected server.

Hedwig works best when you configure the foundation first. You can use
registered slash commands immediately, or use the configured prefix in message
commands. The prefix command is message-only in this build, so use the prefix
form shown below when changing it.

## Command styles

| Style           | Example                                  |
| --------------- | ---------------------------------------- |
| Slash command   | `/help`                                  |
| Prefix command  | `,help`                                  |
| Grouped command | `/antinuke enable` or `,antinuke enable` |

The default prefix in this build is `,`. Server managers can change it with
`,prefix set <new-prefix>` or the equivalent configured-prefix form. A prefix
may be at most 10 characters. `,prefix self <new-prefix>` sets a personal
prefix across servers without changing the server-wide value.

## Five-minute setup

<Steps>
  <Step title="Confirm the bot can respond">
    Run `/ping`. If Hedwig cannot respond, check that it has **View Channel** and **Send Messages** in the channel where you are testing.
  </Step>

  <Step title="Choose a prefix">
    Run `,prefix` to see the current value. Use `,prefix set !` to choose a
    server prefix, `,prefix remove` to restore the project default, or
    `,prefix self ?` for a personal prefix.
  </Step>

  <Step title="Create a safety net">
    Run `/logging setup`, `/automod setup`, and `,antinuke enable` from an
    administrator-only channel. Read [Permissions](/permissions) before
    enabling protection. Antinuke enable is restricted to the server owner or
    an extra owner.
  </Step>

  <Step title="Set up the member experience">
    Pick the systems that fit your server: `/greet setup`, `/leveling setup`, `/ticket setup`, `/selfrole setup`, or `/giveaway start`.
  </Step>

  <Step title="Test each workflow">
    Use each feature's `test`, `config`, or `status` command where available. Test in a private channel before announcing it to members.
  </Step>
</Steps>

## A useful first-week stack

<CardGroup cols={2}>
  <Card title="Small community" icon="seedling">
    Greet & farewell, suggestions, feedback, reminders, polls, and music.
  </Card>

  <Card title="Growing community" icon="chart-line">
    Add leveling, self-roles, giveaways, tickets, tracking, and autoroles.
  </Card>

  <Card title="Public community" icon="building-shield">
    Add antinuke, automod, logging, staff applications, and a documented moderation process.
  </Card>

  <Card title="Creator or media server" icon="broadcast-tower">
    Add autopost, social notifier, music, profile cards, and live leaderboards.
  </Card>
</CardGroup>

<Warning>
  Do not give Hedwig more permissions than the server needs. A bot cannot
  protect a role or channel above its highest role, and a moderation action can
  fail if Discord's role hierarchy blocks it. Never paste a bot token or
  provider key into Discord.
</Warning>

## Find your next step

* Need the bot to **stop raids or destructive actions**? Read [Security](/security/overview).
* Need to **manage members and channels**? Read [Moderation](/moderation/overview).
* Need **tickets, roles, levels, or welcomes**? Read [Community systems](/community/overview).
* Need to **play music**? Read [Music](/music/overview).
* Need a **quick utility or AI tool**? Read [Utility & extras](/utility/overview).