> For the complete documentation index, see [llms.txt](https://docs.pakk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pakk.io/websites/visual-style-guide/icons.md).

# Icons

The icon set used on your website is customisable and can have a big impact on the overall feeling.

<figure><img src="https://2553116242-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkTaBpmn8aX5KjLYTOO52%2Fuploads%2FLcBc9oIgif3u0XPnCy9b%2FScreenshot%202024-10-29%20at%2010.39.16.png?alt=media&amp;token=599ef063-2a32-428a-bcf0-a7bd5db11878" alt=""><figcaption></figcaption></figure>

Icons are used throughout Pakk eCommerce stores.  Whilst you cannot specify which icons are used where, you can choose from a number of high-level icon 'sets':

* **Thin**: A very light and delicate style, ideal for subtle designs where icons shouldn't dominate.
* **Light**: Slightly thicker than Thin, good for minimalistic designs needing a bit more presence.
* **Regular**: The default, balanced weight that works well in most scenarios.
* **Bold**: A thick, strong style that makes icons stand out, perfect for drawing attention.
* **Duotone**: Uses two colors to create a modern, layered effect. The icon’s stroke color will match the text, while the fill color will be a lighter variation of your primary color, adding visual interest.

Choose lighter weights (Thin/Light) for subtlety, Regular for balanced use, Bold for emphasis, and Duotone for modern, eye-catching designs.


---

# 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.pakk.io/websites/visual-style-guide/icons.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.