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

# Image with text

A split layout — image on one side, content on the other — for brand stories, materials, or process. On mobile the image stacks above the content.

👉 **Customize → Add section → Image with text** (on pages that allow sections).

## Settings

* **Image** — the photo; a placeholder shows until you pick one. 1200px wide is plenty.
* **Image position** — `Left` (default) or `Right`. Alternate when stacking several of these sections.

## Blocks

### Heading (max 1)

* **Heading** (default "About the brand").

### Text (max 1)

* **Text** (rich text, default "Tell your story. Share what makes your drops different.").

### Button (max 1)

* **Label** (default "Learn more") + **Link** — an outline button; empty label hides it.

## Pro tip

💡 Stack two of these with alternating image positions ("Left" then "Right") for a magazine-style about page: one on your materials, one on your process. Keep each text block under \~80 words so the image and copy stay the same height on desktop.


---

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