> 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/changelog/october-2024/october-8th-2024.md).

# October 8th, 2024

Starting today, creating interactive demos with videos and voiceovers has never been easier. Whether you’re looking to explain complex concepts or simply add a personal touch to your demos, these new features have got you covered.

### Videos and Voiceovers

Why it matters:

* **Personal Connection:** Let your video or voice guide prospects through the demo.
* **Simplify Complexity:** Videos make tricky concepts easier to grasp.
* **Boost Engagement:** Make demos more interactive and human.

#### Adding videos to your demo&#x20;

Here is an interactive demo on how to add a video to any step in your demo 👇

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

#### Adding voiceovers to your demo

Here is an interactive demo on how to add a voiceover to any step in your demo 👇

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

Visit our [documentation](https://docs.storylane.io/storylane-knowledge-base/editing-demos/videos-and-voiceovers) for detailed steps and tips.

Stay cool and happy demoing! ✌️


---

# 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:

```
GET https://docs.storylane.io/changelog/october-2024/october-8th-2024.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
