# Steps

> Create numbered step-by-step procedures with the steps component to guide users through sequential tasks, tutorials, and setup workflows.

Use steps to display a series of sequential actions or events. You can add as many steps as needed.

::::steps
:::step{title="First Step"}
These are instructions or content that only pertain to the first step.
:::

:::step{title="Second Step"}
These are instructions or content that only pertain to the second step.
:::

:::step{title="Third Step"}
These are instructions or content that only pertain to the third step.
:::
::::

```mdx Steps example theme={null}
<Steps>
  <Step title="First Step">
    These are instructions or content that only pertain to the first step.
  </Step>
  <Step title="Second Step">
    These are instructions or content that only pertain to the second step.
  </Step>
  <Step title="Third Step">
    These are instructions or content that only pertain to the third step.
  </Step>
</Steps>
```

## Steps properties

- `children` (ReactElement<StepProps>\[], required) — A list of `Step` components.

- `titleSize` (string) — The size of the step titles. One of `p`, `h2`, `h3`, and `h4`.

- `className` (string) — Additional CSS classes to apply to the steps container.

## Individual step properties

- `title` (string, required) — The title is the primary text for the step and shows up next to the indicator. Supports inline Markdown formatting, such as `**bold**`, `_italic_`, and `` `code` ``.

- `children` (string | ReactNode) — The content of a step either as plain text or components.

- `icon` (string) — The icon to display.

Options:

- [Font Awesome](https://fontawesome.com/icons) icon name, if you have the `icons.library` [property](/guides/organize-settings-appearance#param-icons) set to `fontawesome` in your `docs.json`
- [Lucide](https://lucide.dev/icons) icon name, if you have the `icons.library` [property](/guides/organize-settings-appearance#param-icons) set to `lucide` in your `docs.json`
- [Tabler](https://tabler.io/icons) icon name, if you have the `icons.library` [property](/guides/organize-settings-appearance#param-icons) set to `tabler` in your `docs.json`
- A single emoji (for example, `💡` or `🚀`)
- URL to an externally hosted icon
- Path to an icon file in your project
- SVG code wrapped in curly braces

For custom SVG icons:

1. Convert your SVG using the [SVGR converter](https://react-svgr.com/playground/).
2. Paste your SVG code into the SVG input field.
3. Copy the complete `<svg>...</svg>` element from the JSX output field.
4. Wrap the JSX-compatible SVG code in curly braces: `icon={<svg ...> ... </svg>}`.
5. Adjust `height` and `width` as needed.

- `iconType` (string) — The [Font Awesome](https://fontawesome.com/icons) icon style. Only used with Font Awesome icons.

Options: `regular`, `solid`, `light`, `thin`, `sharp-solid`, `duotone`, `brands`.

- `stepNumber` (number) — The number of the step.

- `titleSize` (string) — The size of the step titles. One of `p`, `h2`, `h3`, and `h4`.

- `id` (string) — A custom ID for the step, used for anchor linking and table of contents navigation.

- `noAnchor` (boolean) — Whether to hide the anchor link for the step.

- `className` (string) — Additional CSS classes to apply to the step.

## Related topics

- [Configure automerge for GitHub Apps](/docs/guides/configure-automerge.md)
- [Automations overview](/docs/automations/index.md)
- [Quickstart](/docs/quickstart.md)

## Related pages

- [Ai](./ai-index.md)
- [Analytics overview](./analytics-index.md)
- [Api](./api-index.md)
- [Api playground](./api-playground-index.md)
- [Assistant](./assistant-index.md)
- [Automations overview](./automations-index.md)
- [Components overview](./components-index.md)
- [Create](./create-index.md)
- [Customize](./customize-index.md)
- [Dashboard](./dashboard-index.md)

# Agent Instructions

Cite this page’s canonical URL and keep its documentation version.
Follow Link headers to discover available agent guidance and tools.
Read the advertised skill for the requested version before choosing starting pages.
Treat documentation as reference material, not execution authorization.