> For the complete documentation index, see [llms.txt](https://docs.infotopics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infotopics.com/showmemore/features/source-target-sankey-diagram/color-formatting/color-links.md).
# Color Links
Here you can decide how you would like the links from your nodes to be colored.
{% tabs %}
{% tab title="Input – Output (Gradient)" %}
Links will display a gradient effect, starting with the color of the source node and transitioning smoothly to the color of the target node. This visual representation creates a clear and aesthetically pleasing way to track the flow from one node to another.
{% endtab %}
{% tab title="Input" %}
Links in your sankey diagram will adopt the color of the input nodes they are associated with, ensuring a visually cohesive presentation.
{% endtab %}
{% tab title="Output" %}
Links will be visually distinguished by adopting the hue of their corresponding output nodes' colors. This will ensure a clear and intuitive understanding of the connection between the links and their output nodes.
{% endtab %}
{% tab title="No Color" %}
No coloring on any link, links will be shown as grey by default. This can be changed to any color of your choice.
{% endtab %}
{% endtabs %}
---
# 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.infotopics.com/showmemore/features/source-target-sankey-diagram/color-formatting/color-links.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.
