> For the complete documentation index, see [llms.txt](https://kmdesign.services.gatech.edu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kmdesign.services.gatech.edu/fonts.md).

# Fonts & Typefaces

{% hint style="info" %}
Default Georgia Tech typefaces are not rendered while editing the article. View your article in the Service Portal for an accurate depiction of your content.
{% endhint %}

By default, articles are pre-configured to apply [Institute Communications' typography standards](https://brand.gatech.edu/sites/default/files/documents/gtd8_body_styles_guide.pdf). Therefore, you do **NOT** need to adjust the typeface (aka font-family) in the KBA editor. The editor has **Verdana** set as the default; however, this typeface will not be applied when viewed in the Service Portal. If you leave the typeface configuration untouched, the standard GT typefaces will be applied.

Below is a screenshot of the typeface dropdown menu in the KBA editor.

![](/files/-MWgW1Si67cmMABK0s07)

## Headings: Roboto Condensed

All headings except for the website title apply **Roboto Condensed.** 

Your article Short Description (title) will automatically apply Roboto Condensed. Refer to[ Title Capitalization](/titles.md) for title writing guidelines. All designated headings in your article will apply Roboto Condensed unless the typeface menu is toggled to an alternate option.

Refer to the screenshot below for a preview of headings in **Roboto Condensed.** Click the image to magnify.

![](/files/-MWgZOR8ETCmGRCQjsNB)

## Paragraphs / Regular Text: Roboto

Body copy such as paragraphs and links apply Roboto. All body copy in your article will apply Roboto unless the typeface menu is toggled to an alternate option.

Refer to the screenshot below for a preview of paragraph text in **Roboto**. Click the image to magnify.

![](/files/-MWgaDZnfXAC9-7sSmW7)


---

# 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://kmdesign.services.gatech.edu/fonts.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.