> For the complete documentation index, see [llms.txt](https://uxsmart.gitbook.io/velare/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://uxsmart.gitbook.io/velare/set-up-your-store/typography.md).

# Typography

Typography settings decide which fonts your store uses and how large the text is. Vélare splits them into four groups (body, heading, menu and button) so you can pair a readable font for long text with a more distinctive one for headings, and keep navigation and buttons consistent with either choice. Set the fonts once here and every page picks them up, so you never have to restyle text section by section.

### Where to find these settings <a href="#where-to-find-these-settings" id="where-to-find-these-settings"></a>

Go to **Online Store > Themes > Customize > Theme settings > Typography**.

<figure><img src="/files/dQFr3TP5kfxJa6HLiDub" alt=""><figcaption></figcaption></figure>

The typography settings are grouped into the four sections below.

### 1. Body <a href="#body" id="body"></a>

Choose the font used for body text and set its base font size. This is the text customers read most, such as product descriptions, page content and form labels, so favour legibility over personality here.

<figure><img src="/files/QdmTTRQa15MBpNDHQI9l" alt=""><figcaption></figcaption></figure>

### 2. Heading <a href="#heading" id="heading"></a>

Choose the heading font, then adjust the font size scale, text transformation and letter spacing that apply to all headings. The size scale moves every heading level together, so the hierarchy between a page title and a section title stays intact.

<figure><img src="/files/b4W6IoOpRFjolKUbXHRS" alt=""><figcaption></figcaption></figure>

### 3. Menu <a href="#menu" id="menu"></a>

Pick the menu font from the heading and body fonts you already chose, so the navigation stays in the same family as the rest of the store. You can also switch capitalization on or off for first level menu items.

<figure><img src="/files/WjcJa3qXSiT9lEqc8e5F" alt=""><figcaption></figcaption></figure>

### 4. Button <a href="#button" id="button"></a>

Pick the button font from the heading and body fonts you already chose. Buttons carry short labels such as Add to cart, so this choice mainly affects how deliberate those actions look.

<figure><img src="/files/MlyBN5h96lClfkPi7L3q" alt=""><figcaption></figcaption></figure>

### What customers see <a href="#what-customers-see" id="what-customers-see"></a>

Body font and base size set how comfortable your store is to read, and the effect is strongest on mobile and on long product descriptions. The heading font, scale, transformation and letter spacing set the tone of the store: tight uppercase headings read as editorial, larger mixed case headings read as friendly. Menu and button fonts reuse the same two families, so the header, the navigation and every call to action stay visually connected instead of looking like they came from different templates.

### Related pages <a href="#related-pages" id="related-pages"></a>

* [Colors](/velare/set-up-your-store/colors.md): the text and heading colors applied to these fonts
* [Layout](/velare/set-up-your-store/layout.md): page width, which decides how long each line of body text is
* [Header](/velare/set-up-your-store/header-group/header.md): where the menu font is displayed
* [Vélare Intro](/velare/readme.md): overview of the theme and where to start


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://uxsmart.gitbook.io/velare/set-up-your-store/typography.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.