> 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/sharing-demos/conference-mode.md).

# Conference Mode

Prepare conference-ready demos with Storylane

Conferences are pivotal to showcase your product to a live audience. Storylane interactive demos support multiple features to help significantly enhance comprehension and engagement.

* [Offline demos](#offline-demos)
* [Demo autoplay](#demo-autoplay)
* [Fullscreen mode](#fullscreen-mode)

### 👉 Offline demos

Storylane offline demos are a great option for situations like conferences, trade shows, and site visits where internet connectivity may be unreliable. Here’s how it works:

* **Download the demo**: Ensure you have a good internet connection when downloading the demo for offline use. This makes it accessible anytime, directly through a secure URL.
* **Seamless viewing**: Once downloaded, you don’t need to worry about refreshing the page or losing progress if the connection drops. The demo remains fully operational.
* **Ideal for On-the-Go**: Whether you’re on a site visit or in transit, the offline demo lets you showcase your product without the need for internet access.
* **Ready When You Are**: No need to set up or rely on unstable connections—just open the saved URL, and your demo is ready.

(Note: Analytics won’t be captured during offline viewing)

<div align="left"><figure><img src="https://2431356420-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FN8hWd9k2Pbb6YSWO4pUQ%2Fuploads%2FSZadbDRjMjTy9AainuXa%2FScreenshot%202026-02-16%20at%202.01.29%E2%80%AFPM.png?alt=media&amp;token=780691a9-ea22-4d3e-96e2-9fd527f56bca" alt="" width="563"><figcaption></figcaption></figure></div>

{% hint style="warning" %}
**Important Notice:**

When using multiple offline demos simultaneously, please be aware that they ***cannot*** be opened in the same browser tab. Each demo relies on its own dedicated resources, and when multiple demos are opened in the same tab, the second demo will not be able to access the necessary resources. To ensure smooth functionality, we recommend either combining the demos into a single experience or opening each demo in a separate tab.
{% endhint %}

### 👉 Demo autoplay

Auto playing demos is a great way to grab attention to your conference booths. Here's how it works:

1. Open the demo you would like to autoplay.&#x20;
2. Go to demo settings (gear icon at the top) > Behavior.&#x20;
3. Here, you can turn on autoplay and choose the speed of the demo.

<div align="left"><figure><img src="https://2431356420-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FN8hWd9k2Pbb6YSWO4pUQ%2Fuploads%2FxtevuUZRbyDaakLdqArk%2FScreenshot%202026-02-16%20at%202.02.33%E2%80%AFPM.png?alt=media&amp;token=b0629ca8-dd50-4f38-bdb9-23e009f8ed7e" alt="" width="563"><figcaption></figcaption></figure></div>

{% hint style="info" %}
Pro tip: Configure the CTA on the final step of your demo to link back to the first step for an endless demo loop
{% endhint %}

### 👉 Fullscreen mode

If you plan to showcase your screenshot demo in fullscreen, check whether you have enabled a border for your demo. Follow these steps:

1. Open the demo for which you'd like to use in fullscreen
2. Click on demo settings (⚙️) and select framework
3. Ensure it's set to either light or dark
4. Once set, republish and open your demo
5. You'll find a full screen button on your frame

{% hint style="info" %}
If you need help or have any questions, feel free to contact us at <support@storylane.io>.
{% endhint %}


---

# 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/sharing-demos/conference-mode.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.