> For the complete documentation index, see [llms.txt](https://docs.storylane.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.storylane.io/editing-demos/chapters-and-convert-cta.md).

# Chapters & Convert CTA

* [Chapters](#chapters)
* [Convert CTA](#setup-a-convert-cta-button)

***

### 👉 Chapters

Setting up a chapter menu is an excellent way to showcase multiple product features and use cases in a single demo - without overwhelming views with too many steps. To set up a chapter menu:

* Segment your demo steps into multiple chapters (8-10 steps per chapter)
* Select the menu icon to open the chapters 

<div align="left"><figure><img src="/files/BzR2TBCnOBiQNpB8gkPo" alt="" width="375"><figcaption></figcaption></figure></div>

* Select "Setup chapter menu" *(Chapter Menu works best when you have more than 1 chapter)*
* Add or remove chapters as needed

<div align="left"><figure><img src="/files/UG6lr2mcU1H1iXEUQXrF" alt="" width="375"><figcaption></figcaption></figure></div>

* In the "Setup chapter menu" window, switch to the **Behavior & styling** tab to configure how the chapter menu behaves and looks:
  * **Behavior** — choose when the chapter menu button should appear (from the start, or from a specific step), and how it displays the first time a viewer sees it (expand to the middle of the screen, expand in place, or stay collapsed)
* **Design the Chapter Menu Button** — Style the "Button Color" and "Button Text", and configure the position to appear in the left, middle, or right corner. For more customization, fine-tune the offset values. You can also mark chapter menu items as completed once clicked, and choose whether to display the step count next to each chapter.

<figure><img src="/files/gxmqe4N9ABFKVAa6oikr" alt=""><figcaption></figcaption></figure>

By default, Storylane creates a chapter for you when you record a demo. If you want to add new chapters, then click on the next to the chapter name.

View Interactive Demo 👇

{% @storylane/embed subdomain="app" linkValue="7yxdhyi6v3y7" url="<https://app.storylane.io/share/7yxdhyi6v3y7>" %}

***

### 👉 Setup a Convert CTA Button

The Convert CTA button allows you to embed an always-visible CTA button within your demos. This strategic placement ensures that your viewers are constantly primed to take your most desired action, whether it's to book a demo, start a free trial, share a calendar link or any other key conversion event.&#x20;

<figure><img src="/files/irL2lAI4RyOeBgrQmRYQ" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
If you need help or have any questions, feel free to contact us at <support@storylane.io>.
{% 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 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://docs.storylane.io/editing-demos/chapters-and-convert-cta.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.