> 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/scrolling-content.md).

# Scrolling content

Scrolling content  creates a marquee-like section where the text autorotates.

<figure><img src="https://3146423938-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZQuVfmt0J7tzTvfBqG6C%2Fuploads%2FBXqsxCpWvTaF0yFnrWSm%2Fscrolling-content.png?alt=media&amp;token=f14bebd9-8d98-456c-8331-cb10dd8db12a" alt="Four different configurations of thte scrolling content section "><figcaption></figcaption></figure>

{% hint style="info" %}
By default, this section will respect a customer’s animation preferences. If they have disabled motion or animation at the operating system or browser level, this section will not move. If you wish to create a static section for all users, consider using the rich text section and adjusting the padding.
{% endhint %}

### Settings

* **Scrolling speed**: When auto-scroll is selected, choose the scrolling speed
* **Scroll direction:** When auto-scroll is selected, choose betwen to left or to right
* **Gap between content**: Choose a gap between 0px and 100px
* **Typography**:
  * **Font type**: Choose heading or body
  * **Font size**: Manually choose a font size from 12px to 100px

{% hint style="info" %}
The following settings are explained in detail in [common settings](https://docs.ultramarinastudios.com/common-settings.md):

* Color scheme/Color scheme transition
* Padding
* Borders
  {% endhint %}

### Blocks

* **Text**
* **Image**:
  * **Image**: Select/upload an image
  * **Image width**: Between 0px and 200px
  * **Link (optional)**: If you add a link, remember to add alt text to your image that describes the link purpose


---

# 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/scrolling-content.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.
