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

# Ticker

The **Ticker** block shows a **scrolling ticker** of text or content—e.g. a single line of text that moves horizontally (often used for announcements or marquee-style messages).

***

## What you can do

* Add the **content** that scrolls (e.g. a line of text, or multiple items if the block supports it).
* Optionally set **speed** and **direction** (left/right) when those options exist.
* Use it for announcements, partner names, or short rotating messages.

***

## Options

Depending on configuration:

* **Content** — Text or blocks to show in the ticker.
* **Speed** — Scrolling speed.
* **Direction** — Left or right.
* **Pause on hover** — Whether scrolling pauses when the visitor hovers (if supported).

Check the block's panels in StoryPress for the exact options.


---

# 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://storypress.gitbook.io/storypress-docs/content-blocks/ticker.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.