> For the complete documentation index, see [llms.txt](https://docs.lufavo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lufavo.com/roomfolk/theme-settings/typography.md).

# Typography

**Theme settings → Typography**

## Fonts

| Setting                | What it does                                                                                              |
| ---------------------- | --------------------------------------------------------------------------------------------------------- |
| Heading font           | Used for every heading.                                                                                   |
| Body font              | Used for body text, buttons, menus and form fields.                                                       |
| Display heading weight | The weight used for large display headings such as the hero. Medium, Semibold, Bold, Extra bold or Black. |
| Line height            | 90% to 180%. Applies to headings.                                                                         |

Both fonts come from Shopify's font library. Pick the two, and the theme loads the regular, bold, italic and bold-italic of each — so bold and italic text in your product descriptions and blog posts render properly.

**On Display heading weight:** pick a weight your chosen font actually has. If you select Black and the font has no black weight, the browser substitutes the nearest one, and the result may not be what you expected.

## Heading sizes

Each heading level — Heading 1 through Heading 6 — has three settings:

| Setting        | What it does                                                   |
| -------------- | -------------------------------------------------------------- |
| Size           | 70% to 150%, relative to the theme's base size for that level. |
| Letter spacing | -5 to 10. Negative tightens, positive opens up.                |
| Text case      | Default, or Uppercase.                                         |

These are proportional, not absolute. Setting Heading 1 to 120% makes every H1 larger everywhere, and it still scales down on smaller screens. You are adjusting the relationship between the levels, not fixing a pixel size.

Heading 6 defaults to uppercase with wide letter spacing, because it is used for small labels — the "SHOP" heading above a footer column, for instance.

## Body text

| Setting     | What it does  |
| ----------- | ------------- |
| Size        | 80% to 130%.  |
| Line height | 120% to 200%. |

## Accent icon

| Setting     | What it does                                                                      |
| ----------- | --------------------------------------------------------------------------------- |
| Accent icon | The small character shown before every kicker, and inside the hero's main button. |

It defaults to a four-pointed star. Replace it with any character you like, or clear the field to remove it everywhere at once.


---

# 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://docs.lufavo.com/roomfolk/theme-settings/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.