> 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/april-2026/april-30-2026.md). # April 30, 2026 Hey Storylaners! End of month. Here's what shipped - and why it matters for your team. ### Chrome Extension Share, track, and present The extension was always useful for sharing. Now it's a full demo workflow in one place. * View analytics (views, engagement) directly in the extension * Manage and update your demo links on the fly * Jump straight into Presenter Mode for live calls - no context switching If you're in back-to-back calls, this one's for you. {% @storylane/embed subdomain="app" linkValue="2erbnsvon3bd" url="" %} *** ### AI hub creation Creating demo hubs manually takes time. Now you can skip that. With AI Hub Creation, just describe what you need and pick the content you want to include - demos, PDFs, or videos. • Generate a complete hub from a simple prompt\ • Select which demos, PDFs, and videos to include\ • Automatically organize content into relevant sections\ • Get titles updated to match your story and use case {% @storylane/embed subdomain="app" linkValue="iohnpzo08hds" url="" %} *** ### One more thing 👀 We’re actively working on a **new, more polished editor experience**. Today, it’s automatically available to all free and starter users - but things are evolving behind the scenes, and we can’t wait to bring it to everyone soon 🙂 *** Thanks for trusting us.\ If you have any questions, feel free to reach out at .
--- # 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/april-2026/april-30-2026.md?ask=&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.