> 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/february-2026/february-28th-2026.md).

# February 28th, 2026

This release makes your demos more reusable, more flexible, and more powerful.

Introducing...

### Turn any demo into a PDF, doc, or SOP - instantly

Interactive demos are powerful. But sometimes you need:

* A pitch deck
* A training doc
* An internal playbook
* A printable walkthrough
* A slide-ready narrative

Now you can generate all of that - in one click.

Try interactive demo below 👇

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

***

### Copy & paste steps across demos

Previously:\
You could duplicate steps only within the same demo.

Now:\
You can copy/paste steps across different demos and chapters.

***

### Track & zoom improvements

We’ve upgraded the track & zoom behavior.

You can now:

* Zoom into specific screen areas
* Control focus independently from guide positioning
* Highlight exactly what matters - with more flexibility

***

### One more thing 👀

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

Today it's live only for free users - but things are changing behind the scenes, and we can't wait to show it to all users soon 🙂

***

Thanks for trusting us.\
If you have any questions, feel free to reach out at <support@storylane.io>.<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/february-2026/february-28th-2026.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.