> For the complete documentation index, see [llms.txt](https://docs.scribeware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scribeware.com/getting-started/scribeware-and-desktop-basics/adding-hot-links-to-a-narrative.md).

# Adding Hot Links to a Narrative

This shows how you add links to websites and other information into your narratives.

### Hyperlinks to Internet Content

{% embed url="<https://youtu.be/oXJs_GfCA6g>" %}

Hyperlinks allow you to include valuable reference material in your comments without making the report unnecessarily long. Instead of explaining every topic in detail, you can direct your clients to trusted resources for additional information.

#### To create a hyperlink:

1. Find the webpage you want to reference.
2. Write a descriptive sentence or phrase in your comment (avoid using the raw URL as the link text).
3. Highlight the text you want to make clickable.
4. Click the **Link** button in the comment toolbar.
5. Paste the webpage URL into the **URL** field.
6. Click **OK** to create the hyperlink.
7. Test the link to verify that it opens the intended webpage.

#### Best Practices

* Use descriptive link text so your clients know what they're clicking.
* Link only to reputable, stable websites whenever possible.
* Always test hyperlinks before publishing your report. Websites occasionally move or are removed, and broken links can leave a poor impression on your clients.


---

# 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.scribeware.com/getting-started/scribeware-and-desktop-basics/adding-hot-links-to-a-narrative.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.