# Steps

A procedure is a sequence, so `Steps` renders a real ordered list: the numbers are counters, not decoration, and screen readers announce the structure correctly.

## A procedure

Copy `.env.example` to `.env` and set a password. Everything else has a working default.

```bash
docker compose up
```

Steps hold any content: prose, code blocks, callouts, images.

The site answers on port 4321. A `Check` callout closes a procedure well.

## Usage

```mdx
<Steps>
  <Step title="Create the environment file">
    Copy `.env.example` to `.env`...
  </Step>
  <Step title="Start the stack">
    ...
  </Step>
</Steps>
```

## Props

| Prop    | On     | Type   | Effect                                   |
| ------- | ------ | ------ | ---------------------------------------- |
| `title` | `Step` | string | The step's headline; the body elaborates |

Number steps only when order carries information. A list of independent options set as steps reads as a required march; use a plain list instead.