> For the complete documentation index, see [llms.txt](https://docs.openbrim.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openbrim.org/templates/cadd/text-cadd.md).

# Text

A **Text** annotation places a free-form text block in a CAD document — labels, notes, callouts, sheet titles, view titles, anything that isn't a dimension or a leader note. For text with a leader arrow pointing at a feature, use a Note instead.

## Content

**Text:** The text content. Multi-line is supported.

## Sizing and alignment

**Size:** Text size in real units (e.g., `0.1 m` or `0.3 ft` for \~3 mm or 1/8" plotted text at 1=10 scale).

**Width / Height:** Bounding box dimensions. Text wraps to fit the bounding box width if needed.

**Text Align (horizontal):** Left, Center, or Right. Center is typical for view titles; Left for body text and labels.

**Text Align V (vertical):** Top, Middle, or Bottom alignment within the bounding box.

## Styling

**Level:** Layer assignment. Route to a "Notes" or "Text" level so all text on a sheet picks up consistent styling.

**Color / Thickness / Line Style:** Override the level's styling for this specific text.

## Notes

For sheet titles and view titles, use a larger Size and bold weight (set on the level).

For dense body text (general notes, construction notes), keep size at the project's standard text height for readability at print scale.

Text doesn't snap to underlying geometry — it's a free placement. Position by clicking. Drag to move.


---

# 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.openbrim.org/templates/cadd/text-cadd.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.