> 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/updates-for-november-2022/november-7-2022.md).

# November 7, 2022

### Improvements

*  **WYSIWYG editing for guides and tooltips:** You can customize the widgets in your demos with additional text editing capabilities:
  * **Rich text:** Update a part or the entire text with different colors, bold, *italic*, heading style, etc.
  * **Add hyperlink:** Link a section of text to an external URL or to a different demo as well.
  * **Create a bullet list:** Display text in a bullet point format. 

<figure><img src="https://3394459751-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcTuGT7bBECFxxMZpWaFG%2Fuploads%2FDBA0NlKP8M9oFXqCJBTX%2FScreenshot%202023-01-24%20at%2011.24.44%20AM.png?alt=media&amp;token=c15f4e47-a81b-4db7-acd2-d224f244f72e" alt=""><figcaption><p>Additional text editing features for widgets. </p></figcaption></figure>

* **Share Embed code size:** Improved the popup share embed code to fit windsizing
* **Add multiple images in the demo editor:** Users can drag or drop multiple images into the demo editor. Additionally, they can also choose to add images from their file explorer.&#x20;


---

# 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/updates-for-november-2022/november-7-2022.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.