> 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-7.md).

# Hero #7

### Component Structure

* **COPY WRAPPER (div)**: This foundational layer organizes the Hero #7 component without applying specific styling.
* **HR7 COMPONENT (section)**: Utilizes the `hr7__component` class for full viewport height and centralized content alignment.
* **HR7 CONTAINER (container)**: Marked with `hr7__container`, it holds the component's main elements for structured presentation.
  * **HR7 HEADING (heading)**: Delivers the primary message using `hr7__heading`, positioned for immediate attention.
  * **HR7 TEXT (text-basic)**: Provides supporting information with `hr7__text`, enhancing the message conveyed by the heading.
  * **HR7 BUTTON (button)**: Features a primary action for users, styled with `hr7__button` and `bm__btn` for visibility and interaction.
  * **HR7 IMAGE (image)**: Visual element that complements the textual content, using `hr7__image` for stylistic integration.

### Animation Structure

**HR7 - PAGELOAD**: Sequential animations enhance the entry of `.hr7__heading`, `.hr7__text`, `.hr7__button`, and `.hr7__image`. These elements initially appear with reduced opacity and a slight vertical offset, transitioning to full opacity and alignment for a dynamic page load effect.

**HR7 - IMAGE**: A specific animation for `.hr7__image` on scroll, making the image rotate slightly for an interactive visual effect. This scroll-triggered animation adds depth to the user's engagement with the hero component.


---

# 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-7.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.