> For the complete documentation index, see [llms.txt](https://docs.lufavo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lufavo.com/frameora/sections/hero.md).

# Hero

The Hero section is the main banner area, usually shown near the top of the home page.

Use this section to introduce the store, show a strong product or lifestyle image, and guide customers to important products or collections.

### Open Hero settings

{% hint style="success" %}
To edit the Hero section:

* From your Shopify admin, go to **Online Store > Themes**.
* Find **Frameora**.
* Click **Customize**.
* Open the page that contains the Hero section.
* Select **Hero** in the theme editor sidebar.
* Edit the settings.
* Click **Save**.
  {% endhint %}

***

### Kicker

Use the **Kicker** field for short text above the main heading.

Example:

**Stick. Restick. Smile.**

Keep this text short and memorable.

***

### Heading

The Hero heading is split into three fields:

* Heading line 1
* Heading line 2
* Heading line 3

This gives you more control over the visual layout of the main message.

Example:

**Heading line 1:** Turn your memories\
**Heading line 2:** into beautiful\
**Heading line 3:** stickable photo tiles

Use clear wording that explains what your store sells.

***

### Subheading

Use the **Subheading** field to add a short supporting message below the main heading.

Example:

**Upload your favorite photos and create premium wall tiles that stick, restick, and remove cleanly without nails or wall damage.**

Keep the subheading focused on the product benefit.

***

### Hero image

Use the **Hero image** setting to upload the main image shown in the Hero section.

For best results:

* Use a high-quality image.
* Choose an image that clearly represents your product.
* Avoid images with important details too close to the edges.
* Preview the section on desktop and mobile.

***

### Primary button

The primary button should link to the main action you want customers to take.

Settings include:

* Primary button label
* Primary button link

Example:

**Primary button label:** Create Your Tiles\
**Primary button link:** Your custom photo tile product page

***

### Secondary button

The secondary button can link to another important page, such as a collection.

Settings include:

* Secondary button label
* Secondary button link

Example:

**Secondary button label:** Shop Wall Art\
**Secondary button link:** Your wall art collection

***

### Badges

The Hero section includes three small badge text fields.

Use these badges to highlight short benefits or trust points.

Settings include:

* Badge 1 text
* Badge 2 text
* Badge 3 text

Examples:

* Resticks anytime
* No nails or damage
* Made for real memories

Keep badge text short so it stays readable on mobile.

***

### Save your changes

After editing the Hero section, click **Save**.

Preview the section on desktop and mobile before publishing changes.


---

# 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://docs.lufavo.com/frameora/sections/hero.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.