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

# Before/after image

The before/after image section is often used by beauty brands to highlight the results of their products. Sliding the range to the start reveals the after image fully.

<figure><img src="https://3146423938-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZQuVfmt0J7tzTvfBqG6C%2Fuploads%2FP4QZrnm8vONZLf12ml3j%2Fbefore-after-image.jpg?alt=media&amp;token=c367b0f2-1ddd-43aa-9f9d-20863f9caef0" alt="Before/after slider showing a close-up of a model&#x27;s skin with blemishes on the left and glowing skin on the right"><figcaption><p>Before/after image on Primavera theme</p></figcaption></figure>

### Settings

* **Label style**: For the "Before" and "After" labels, choose between **primary**, **secondary** or **text** (similar to button styles)
* **Label position:** Choose between **top** or **bottom**

### Blocks

This section comes pre-loaded with four types of blocks:

* [Section header](/blocks/section-blocks/section-header.md) (hidden by default, fill in the settings to display)
* **Before**
  * **Image**: Upload the image that corresponds to the before image
  * **Label**: e.g. Before
* **After**
  * **Image**: Upload the image that corresponds to the after image
  * **Label**: e.g. After
* [Buttons](/blocks/buttons.md) (hidden by default, fill in the settings to display)

{% hint style="info" %}
Can't find the setting you're looking for?  The following settings are explained in detail in [common settings](/common-settings.md):

* Container type
* Color scheme/Color scheme transition
* Padding
  {% endhint %}


---

# 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://docs.ultramarinastudios.com/sections/before-after-image.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.