> 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/circular-sankey-diagram/format.md).

# Format

#### Node width

Increase and decrease the width of your nodes using the slider. This will also change the size and shape of your links to in the view.

#### Vertical node padding

Increase and decrease the vertical padding using the slider. This will give the same space between each node (vertically)

#### Horizontal node padding

Increase and decrease the horizontal padding using the slider. This will give the same space between each node and the link.

#### Link opacity

Increase and decrease the link opacity using the slider. 100 will give no opacity, 0 will give the most opacity.

#### Node opacity

Increase and decrease the node opacity using the slider. 100 will give no opacity, 0 will give the most opacity.

#### Node border

Hit ‘Enabled’ to give all your nodes a border.

#### Labels position

Decide the position of your nodes label being inside or outside your node.

#### Hide nulls

Have the ability to hide all nulls by hitting ‘disabled’. The image is showing how you can have flows from column 1 to column 4 with nulls in columns 2 & 3. Nodes can also start and end on different levels.


---

# 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/circular-sankey-diagram/format.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.