# Hero3

{% hint style="info" %}
All available props for the Hero3 component are defined and handled within **Component usage path** file. This allows for easy modifications to the content of the hero section.
{% endhint %}

**Component path**: `src/blocks/hero/Hero3.tsx`

**Component usage path:**  `src/app/blocks/hero/hero3/page.tsx`

**Preview link:** [**https://www.saasable.io/blocks/hero/hero3**](https://www.saasable.io/blocks/hero/hero3)

## Props Details

| Prop Name       | Type                                                          | Description                                                         | Displayed as                                                                                                                                 |
| --------------- | ------------------------------------------------------------- | ------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
| **chip**        | `{ label: ChipProps['label']; link?: LinkProps; }` (Optional) | Optional chip with text and optional link.                          | `{ label: "New Feature", link: { href: "/features", passHref: true } }`                                                                      |
| **headLine**    | `string \| ReactElement`                                      | Main headline for the hero section. Can be text or a React element. | `"Effortless CRM Management, Seamless BusinessGrowth"`                                                                                       |
| **boxImage1**   | `ImageCommonProps`                                            | Image path or object with `light` and `dark` image path.            | <p><code>"path-to-image1.svg"</code><br> or <br><code>{ light: 'path-to-image1-light.svg', dark: 'path-to-image1-dark.svg' }</code></p>      |
| **boxImage2**   | `ImageCommonProps`                                            | Image path or object with `light` and `dark` image path.            | <p><code>"path-to-image2.svg"</code><br> or <br><code>{ light: 'path-to-image2-light.svg', dark: 'path-to-image2-dark.svg' }</code></p>      |
| **boxImage3**   | `ImageCommonProps`                                            | Image path or object with `light` and `dark` image path.            | <p><code>"path-to-image3.svg"</code><br> or <br><code>{ light: 'path-to-image3-light.svg', dark: 'path-to-image3-dark.svg' }</code></p>      |
| **listData**    | `ListDataProps[]` (Optional)                                  | Array of list items with titles and optional links.                 | `[{ title: "Feature 1", link: { href: "/feature1", passHref: true } }, { title: "Feature 2", link: { href: "/feature2", passHref: true } }]` |
| **description** | `string` (Optional)                                           | Optional description text.                                          | `"Discover the amazing features of our new product range."`                                                                                  |
| **exploreBtn**  | `ButtonProps` (Optional)                                      | Optional properties for an "Explore" button.                        | `{ children: "Explore Now", href: "/explore", variant: "outlined", size: "small" }`                                                          |


---

# 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://phoenixcoded.gitbook.io/saasable/ui-kit/development/components/hero/hero3.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.