> For the complete documentation index, see [llms.txt](https://bricksmotion.gitbook.io/bricksmotion-components/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bricksmotion.gitbook.io/bricksmotion-components/components/heroes/hero-6.md).

# Hero #6

### Component Structure

* **COPY WRAPPER (div)**: Encapsulates the Hero #6 component, organizing its structure without applying specific styling.
* **HR6 COMPONENT (section)**: Acts as the main section, using the class `hr6__component` to ensure full viewport height coverage and central alignment of the content.
* **HR6 CONTAINER (container)**: Directly contains the hero's main elements, marked with `hr6__container` for content alignment and positioning.
  * **HR6 CONTENT (div)**: Central content area containing the headline, text, and button, structured for optimal readability and user engagement.
    * **HR6 HEADLINE (heading)**: Delivers the key message with impactful typography.
    * **HR6 TEXT (text-basic)**: Provides additional information or context.
    * **HR6 BUTTON (button)**: Encourages user interaction with a clear call-to-action.
* **HR6 IMAGE WRAPPERS (div)**: Multiple wrappers (`hr6__image-wrapper1`, `hr6__image-wrapper2`, `hr6__image-wrapper3`) contain various images, positioned and styled to complement the hero's content and add visual depth.

### Animation Structure

* **HR6 - PAGELOAD**:
  * Targets `.hr6__content > *` and `.hr6__image` for initial visibility and position animations, enhancing the content's entrance on the webpage.
* **HR6 - SCROLL**:
  * Activates scroll-triggered animations for `.hr6__image-wrapper1`, `.hr6__image-wrapper2`, and `.hr6__image-wrapper3`, moving the images vertically to create an immersive parallax effect. The animations vary in duration and effect, contributing to a dynamic and engaging user experience as they scroll through the hero section.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://bricksmotion.gitbook.io/bricksmotion-components/components/heroes/hero-6.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.