> For the complete documentation index, see [llms.txt](https://docs.realmacsoftware.com/elements-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.realmacsoftware.com/elements-docs/elements-language/component/properties-json/ui-controls/theme-font.md).

# Theme Font

Displays the Theme Studio Font control.

{% tabs %}
{% tab title="Control Example" %}

```json
{
  "title": "Headline Font",
  "id": "headlineFont",
  "themeFont": {
    "default": {
      "base": { "name": "heading" },
      "sm": { "name": "heading" },
      "md": { "name": "display" }
    }
  }
}
```

{% endtab %}

{% tab title="Group Example" %}

```json
{
  "groups": [{
    "title": "Typography",
    "properties": [{
      "title": "Headline Font",
      "id": "headlineFont",
      "themeFont": {
        "default": {
          "base": { "name": "heading" },
          "sm": { "name": "heading" },
          "md": { "name": "display" }
        }
      }
    }]
  }]
}
```

{% endtab %}
{% endtabs %}

For effective theme integration in RapidWeaver Elements, it is recommended to use the `themeFont` attribute to define all font family settings for your elements. This approach ensures that font preferences are coordinated with the overall theme settings, providing a consistent user experience.

### Supported Options

The themeFont control supports the following options.

| Key       | Type   | Notes                                                                                                                                     |
| --------- | ------ | ----------------------------------------------------------------------------------------------------------------------------------------- |
| `default` | object | Per-breakpoint defaults (`base`, `sm`, `md`, …). Each breakpoint holds the `name` of a font from the theme, e.g. `{ "name": "heading" }`. |

### Value

In templates, `{{id}}` outputs the font utility classes for the selected theme font, prefixed for each breakpoint the user has configured. With the example configuration above, referencing `{{headlineFont}}` would output: `font-heading sm:font-heading md:font-display`.


---

# 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.realmacsoftware.com/elements-docs/elements-language/component/properties-json/ui-controls/theme-font.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.