> For the complete documentation index, see [llms.txt](https://staylime.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://staylime.com/docs/volume-themes/sections/banners/split-banner.md).

# Split Banner

Volume's Split Banner section puts two independent banners side by side — ideal for shop-by-category pairs, gender splits, or before/after stories.

Two stories, equal weight. Split Banner puts two independent banners side by side, each with its own image, message, and call to action — the layout shoppers instinctively read as "pick a path." It's the natural fit for men's/women's, new-in vs. bestsellers, or a values statement paired with a shop-now CTA.

***

### How to add

In the Theme Editor, click **Add section** → **Split banner**. It arrives with two **Banner** blocks already in place — configure each side independently.

### Good to know

* **Exactly two banners, no more.** Split Banner is capped at two blocks by design — if a third category needs a tile, that's what **Banner Grid** is for.
* **The whole banner is clickable via Link**, independent of the button. A side doesn't need a visible button to be tappable — set Link on the banner block and turn **Show button** off for a cleaner, button-free look that still takes shoppers somewhere.
* **Show image isn't just Image vs. off** — there's also an **Icon** option, which swaps the visual for a small icon plus color, or a context image. That's a quick way to turn one side into a value-prop tile (e.g. a large shipping icon + "Free worldwide shipping") instead of a second photo.

### Customization ideas

* Pair one photographic side with an **icon-based** side for a magazine-style contrast — product photo on the left, bold icon + short copy on the right.
* Use **Wide** content width only with a short heading — it's built for punchy statements, not paragraphs.
* Set independent **overlay** values per side so a light and a dark photo both keep readable text without matching each other's mood.

***

### Settings reference

| Setting                    | What it does                                                                         |
| -------------------------- | ------------------------------------------------------------------------------------ |
| Overlap                    | Sits the banner under a transparent header                                           |
| Show content only on hover | Reveals each side's text only on hover                                               |
| Height (desktop / mobile)  | Adapt, Pixels, or Percents, set per device                                           |
| Content width              | Narrow, Regular, or Wide                                                             |
| Background animation       | Default, Disable, or Custom — Parallax, Zoom in, or Zoom out (no Sticky option here) |

#### Each Banner block

| Setting                                   | What it does                                                       |
| ----------------------------------------- | ------------------------------------------------------------------ |
| Image (+ mobile image), Link              | The side's background and click destination                        |
| Center text, vertical/horizontal position | Where and how the content sits                                     |
| Overlay (desktop/mobile)                  | Independent overlay color/opacity per device                       |
| Show image                                | Disable, Image, or Icon — a plain visual, or an icon/context image |
| Heading, text                             | Independent show/hide + style per field                            |
| Show button, label, icon, style           | Solid or Outlined, with an optional icon                           |

### Best practices

* Keep both images the same aspect ratio so the split reads as one balanced section.
* If one side needs a different call to action than the other, that's exactly what the two independent Banner blocks are for.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://staylime.com/docs/volume-themes/sections/banners/split-banner.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.