> 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/november-2024/november-11th-2024.md).

# November 11th, 2024

This release focuses on enhancing your demo editing toolkit, giving you more control and flexibility over video elements.

### **✂️ Video Trim**

Keep it sharp! Our enhanced **Trim** feature lets you cut out unnecessary moments from the start and end of your clips, so every second of your demo counts. Polish your message and make sure viewers see exactly what you want them to.

Here is an interactive demo of how it works 👇

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

### **🔀 Split Video to Add Interactivity**

Break it up! Now you can **Split** videos and insert hotspots for a more interactive experience. This feature allows you to weave in explanations or CTAs exactly where they’ll have the most impact, keeping viewers engaged and on track.

Here is an interactive demo of how it works 👇

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

Visit our [documentation](https://docs.storylane.io/storylane-knowledge-base/editing-demos/guides-and-flows/adding-guided-steps/editing-video-clips) 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.storylane.io/changelog/november-2024/november-11th-2024.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.