# December 12th, 2024

Hi there, Storylaners! 👋

Before we head off to an offsite in sunny Bali to recharge and plan for an even bigger year ahead, we couldn’t resist dropping another bundle of product updates. In this release, we are introducing:

### 🎬 Chapters – Tailored for Different Stakeholders

Say hello to **Chapters**, which is an upgrade to the old Flows feature! This refreshed interface makes organizing your demo into multiple chapters tailored to different stakeholders easier.

<div align="left"><figure><img src="https://3394459751-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcTuGT7bBECFxxMZpWaFG%2Fuploads%2FtWyBq3f89RwetH2mHXOo%2FScreenshot%202024-12-09%20at%2013.36.11.png?alt=media&#x26;token=37bf47fc-de44-4be1-9f77-a1377b985e5a" alt="" width="563"><figcaption></figcaption></figure></div>

### 🔒 **External APIs**

For power users and developers, we’ve introduced external API capabilities that allow seamless backend integration with Storylane. With these APIs, you can:

* **List published demos** for easy access and tracking.
* **Create demo links** with advanced security controls like passcodes, expiration dates, or authentication codes.
* **Pass email parameters** as optional fields in demo links for better personalization.
* **Update links** with tokens for secure access.
* **View active links** and disable them when needed.

### 🚀 Other Updates

* A refreshed **Extension UI** for smoother navigation and easier access to key tools.
* &#x20;**Speed improvements in the Editor**, so building demos feels like Santa’s sleigh on turbo mode. 🛷 (oh, yes, #ChristmasModeActivated 🎄)

Stay cool and happy demoing! ✌️


---

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