> 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/december-2024/december-29th-2024.md).

# December 29th, 2024

Hi there, Storylaners! 👋

As we close out the year, we’re excited to deliver one final set of updates to make your demos more seamless and insightful.

### 🚀 **Time-Based Trigger: Step Autoplay for Smoother Navigation**

Keep your audience engaged without manual clicks! With the new **Trigger function** in both **screenshot demos** and **HTML demos**, guides can now progress automatically after a set period of time.

* **Where to Find It:** Edit guide > Trigger.
* **How It Works:** Once added, the guide moves forward automatically after the defined duration.
* **Available In:** Hotspots and Tooltips.
* ![](https://3394459751-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcTuGT7bBECFxxMZpWaFG%2Fuploads%2FAxVAL51CoE3mSVPqYWl9%2FScreenshot%202025-01-01%20at%2011.47.25.png?alt=media\&token=9301e16a-1ff2-4444-bedb-a851dad1019b)

### 📊 **Chapter-Level Insights with GA and Cross-Frame Events**

We’re now sending **sl\_chapter\_start** and **sl\_chapter\_end** events to Google Analytics and as Cross-Frame events. We will be deprecating flow events soon.

* **New Events:** `sl_chapter_start`, `sl_chapter_end`
* **Deprecating Soon:** `flow_start` and `flow_end`

### 🖼️  **WebP Image Support**

You can now upload **WebP images** directly into your demos. Smaller file sizes and faster load times – it’s a win-win-win!&#x20;

Why WebP? Better compression, reduced loading time, and clearer visuals.

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/december-2024/december-29th-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.
