> For the complete documentation index, see [llms.txt](https://docs-v3.toucantoco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-v3.toucantoco.com/visualizations-and-layouts/creating-visualizations/advanced-chart-configuration/navigate-with-stories.md).

# Navigate with stories

How to :: navigate with stories

### LinkTo overview

A story can be linked to one or two stories or the home page using the linkTo option. You can even use external links! 🔥

<figure><img src="https://1809014303-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZxYYf1KpgarKMgMsDCrw%2Fuploads%2Fgit-blob-f210fab29134673dd044be89665e60125ab5b1ee%2FScreenshot%202023-09-20%20at%2014.42.29.png?alt=media" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
Warning

This feature is powerful, but it can make the navigation within your application confusing. Therefore, we have limited the number of links to two.
{% endhint %}

### Configuration

{% hint style="warning" %}
Warning

This option is only available in code mode.
{% endhint %}

You can use HTML syntax for the legend (this allows you to add pictograms, for example): \<i class="fa fa-list" aria-hidden="true">\</i> Go to list view

The link buttons and the story narrative are positioned in the same place. Do not use both in the story. Also, make sure to test it on mobile devices as well 📱.

### Link to a story

If you want to link a story to another story, there are only three parameters you need to set up:

* `legend` : the text that will be displayed on a button.
* `targetLayoutId` : enter the ID of the story. You can find it in the URL of your story.
* `targetLayoutType` : the type of layout you want to link to in this case STORY.

```coffeescript
linkTo: [
  {
    InternalLink:
      legend: "Go to rank evolution"
      targetLayoutId: "dabe4b16-c292-4612-8647-59caf9eee995"
      targetLayoutType: "STORY"
  }
  {
    InternalLink:
      legend: "Go to highest rated"
      targetLayoutId: "2a44759d-15d1-4873-8ee7-58f3d8ec2fc0"
      targetLayoutType: "STORY"
  }
]
```

### Link to the home

If you want to link a story to the home page, there are two parameters you can set up:

* `legend` : the text that will be displayed on the button.
* `targetLayoutType` : the type of layout you want to link to, in this case "HOME".

```coffeescript
linkTo: [
  {
    InternalLink:
      legend: "Link to the home"
      targetLayoutType: "HOME"
  }
]
```


---

# 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-v3.toucantoco.com/visualizations-and-layouts/creating-visualizations/advanced-chart-configuration/navigate-with-stories.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.
