> 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/may-2025/may-8th-2025.md).

# May 8th, 2025

If you’re short on time (who isn’t?), the newest updates were built with you in mind - faster edits, fewer interruptions, and smoother everything.

Let’s dive in 👇

### 🧠 Smarter AI for Existing Demos

We’ve upgraded our “**Create with AI**” flow ✨\
Now, when you add new screens to an *existing demo*, our AI will auto-generate content just for those steps - without reprocessing the entire demo.

### ✨ Smoother AI HTML Editing

Working with HTML demos just got easier.\
We’ve optimized AI-powered HTML editing so it feels lighter, faster, and less frustrating.

*  Faster AI generation
*  No more AI editor slowdowns

<div align="left"><figure><img src="https://3394459751-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcTuGT7bBECFxxMZpWaFG%2Fuploads%2F1hDTlPAL1t4iAEBOgHb7%2FScreenshot%202025-05-22%20at%2014.37.59.png?alt=media&amp;token=047dce24-2738-428f-9ced-5c1494e8d987" alt="" width="563"><figcaption></figcaption></figure></div>

### ⚡ Faster Analytics Dashboards

We shaved off precious seconds so you get your data faster.\
No more waiting — just open your dashboard and *boom*, insights ready to go.

* Quicker load times
* &#x20;Smoother performance

### 🚀 Improved Text Recognition in the Extension

We’ve improved how Storylane’s extension detects and reads on-screen elements like:

* Lists
* Radio buttons
* Checkboxes

This means cleaner, more accurate guide content, especially for form-heavy screens.<br>


---

# 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/may-2025/may-8th-2025.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.