# January 12th, 2026

We’ve shipped a bunch of small-but-important updates recently with a goal to make building, watching, and analyzing demos smoother.

Here’s what’s new 👇

### Scroll to a specific element in HTML demos

If you’re linking screens in an HTML demo, you can now choose *exactly* where the viewer lands on the next screen.

Instead of dropping them at the top, Storylane will auto-scroll to the element you care about.

This is especially useful when:

* The page is long
* You want to highlight one specific UI element
* You don’t want to add extra steps just to explain where to look

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

***

### Video player performance improvements

We’ve done a pretty big cleanup and optimization of the video player.

You won’t see any UI changes here - but things should feel faster and more stable, especially on longer demos and across devices.

If your demos felt a bit more “snappy” lately, this is why.

***

### CSV exports for sessions, leads, accounts

Before, exporting data always gave you the same CSV, no matter where you were.

Now exports are **page-specific**:

* CSV export of all **sessions**&#x20;
* CSV export of all **leads**
* CSV export of all **accounts**&#x20;

***

### More editing options in Hubs

We added a few extra editing controls in Hubs - including the ability to adjust the **lead form size**.

Small thing, but it gives you more flexibility when you’re trying to balance the Hub layout.

***

### One more thing 👀

We’re actively working on a **new, more polished editor experience**.

It’s not live yet, so nothing to try today - but things are changing behind the scenes, and we can't wait to show it to you soon 🙂

***

Thanks for trusting us.\
If you have any questions, feel free to reach out at <support@storylane.io>.<br>


---

# Agent Instructions: 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/january-2026/january-12th-2026.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.