> 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/apps/customizing-apps/adding-glossary.md). # Adding Glossary ## Overview At Toucan, we believe in sharing more than data: we share stories. Stories need content and explanations. Good stories push you to take action! That’s why we have the [Collaboration Panel](https://github.com/ToucanToco/doc-v3/tree/main/visualizations-and-layouts/apps/customizing-apps/broken-reference/README.md). From this panel, you can make a **Glossary** available to all your users 📖 . You can specify a glossary for your whole application. Terms can be specific to a story or common to several or all. 🔥 Awesome tool for strong data storytelling, right? ## Create a glossary Terms can be set up at the **story** level directly from the Studio. 1. Click on the "Glossary" menu left-hand navigation from a Story.

2. Click on "Add New Definition"

3. Write the Term label and the definition related to it. Always better with a definition.\\

If you want this definition accessible throughout your apps from any Story, tick "Make entry available on all stories." It will appear in Staging with a greyed tickbox on the right side.

#### 🌍 Language in the Glossary :: How to manage different languages? If you want to add a glossary in different languages: Please check the documentation about the languages 💡 You can apply translations in your terms title and their description. {% hint style="info" %} **Hint** Want a term’s definition on your home page? Why not use the text tile for it? {% endhint %} --- # 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/apps/customizing-apps/adding-glossary.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.