> 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/ridgeline-plot/labels.md).

# Labels

#### Number format

Format your measure to a decimal or a percentage using the dropdown menu. Enter the amount of decimal spaces shown under ‘decimals’. Add a ‘Prefix’ and/or a ‘Suffix’ in the text boxes. A prefix will go before the word and the suffix after. A prefix for example could add a currency ‘$’ and a Suffix could add a ‘%’.

#### Display units (Decimal only)

Within your data there could be large values. Here you can format using separators. Use the dropdown menu to display numerical units. Example: 6,744 – 6.74K. Use the tick box to include thousands separators. Example: 1234 – 1,234.

#### Font size

Use the dropdown menu to change the size of the font from 50% – 150%. Changing the font size will affect all fonts within your Ridgeline Plot.

#### Font family

Use the dropdown menu to change the font best to suit your dashboard.

#### Font color

Clicking on the circle shapes will open the color palette. Nodes, Links and Headers can all be changed separately using their own palette.

<br>


---

# 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/ridgeline-plot/labels.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.