> For the complete documentation index, see [llms.txt](https://sitesbyseth.gitbook.io/sitesbyseth-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sitesbyseth.gitbook.io/sitesbyseth-docs/showcase/sections/image-banner.md).

# Image banner

A classic hero: a full-width image with an optional dark overlay and up to three content blocks (heading, text, buttons) positioned over it. Useful on standard pages — remember the homepage itself is the story deck and doesn't take extra sections.

👉 On any page that allows sections: **Customize → Add section → Image banner**.

## Settings

* **Image** — the banner image; a placeholder shows until you pick one. 2400px wide recommended.
* **Banner height** (30–100vh, default 70vh) — as a share of the screen height. 100vh = full screen.
* **Overlay opacity** (0–80%, default 20%) — dark tint for text legibility.
* **Text color** (default `#FFFFFF`) — for all content on the banner.
* **Content alignment** — left / center / right text alignment (also positions the content horizontally).
* **Vertical position** — `Top`, `Middle` (default), or `Bottom`.

## Blocks

### Heading (max 1)

* **Heading** (default "New arrivals").

### Text (max 1)

* **Text** (default "Limited drops. No restocks.") — one short line; it caps at a readable width.

### Buttons (max 1)

* **First button label** (default "Shop now") + **First button link**.
* **First button style** — `Solid` or `Accent` (default; uses your accent color).
* **Second button label** + **Second button link** — always outline-styled; leave the label empty to show one button.

## Pro tip

💡 Put the focal point of your image in the safe zone opposite your content position — content bottom-left, subject right. And at 100vh height with a heading + one button, this section doubles as a landing-page hero for link-in-bio pages.


---

# 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://sitesbyseth.gitbook.io/sitesbyseth-docs/showcase/sections/image-banner.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.