# Steps

The Steps Module is designed to display a series of ordered steps, each containing an image, heading, and description, to guide users through a specific process. This module is ideal for showcasing customization processes or any sequence where users need step-by-step guidance.

<figure><img src="/files/HkziWOZHZBdYtOq28X9w" alt=""><figcaption></figcaption></figure>

**Features**

1. **Image**: Upload an image for each step to provide users with a visual understanding of the current step.
2. **Heading**: Set a concise title for each step to give users a quick overview of the step’s purpose.
3. **Description**: Provide a detailed explanation of each step’s specific information or actions to help users understand and complete it.

**Settings**

1. **Number of Steps**: You can add up to 4 steps (blocks). Each step is an independent block that can be added, edited, or removed as needed.
2. **Order of Steps**: Steps are displayed in the order they are added, ensuring users can follow the intended sequence.
3. **Content Editing**: Customize each step's content through the "Image," "Heading," and "Description" fields, offering a clear and organized guide for users.

**Usage Recommendations**

* **Image Selection**: Use images that are relevant to each step to enhance visual clarity.
* **Concise Headings and Descriptions**: Keep headings brief and to the point. Descriptions can be more detailed but should avoid unnecessary length to ensure easy understanding.
* **Ideal for Complex Processes**: This module is perfect for illustrating product customization, service workflows, or project milestones, helping users understand each step in the process.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://ascent.webvista.studio/sections/steps.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.