# Textarea
A **Textarea** input provides a small, multi-line rich text editor with very basic formatting options:\
bold, italic, underline, supertext, subtext, Link and very dear option Soft Hyphen (``) for when you want to insert a "-" in long words that may or may not risk breaking your design on various screen sizes. For further elaboration read this [article](https://alpaco.email/blog/An-ode-to-Soft-hypen).
The input type also gives users access to an **Emoji dropdown** of various glyphs and icons to insert in their text.
Furthermore This input type has the option of creating a **Link style**, so you can inject the css styling for all links created in that textarea. These settings are found in the foldout called "Advanced" below each Textarea. Link styling also allows for liquid variables, so you can dynamically change stylings based on template rules e.g.\
`color: {{ textcolor }}; text-decoration: underline;`\
\
Additionally we allow for **custom text stylings** in the options dropdown. This is particularly helpful for situations where you want to give the user an ability to use some custom text formatting, but only within the specific limits you set them to, for instance:\
`font-size:35px;`*.*\
\
*In order to use this feature properly it's important that the CSS values are valid.*
Individual text styling options like bold, Italic, soft-hypen ect. can be disabled from the template editor foreach textarea input.
Works great for:
* Body/content texts
* Custom styled text inputs with specific design limitations
### Template editor
This is how it looks in the Template Editor
### Email editor
This is how it looks in the Email Editor
---
# Agent Instructions: 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:
```
GET https://documentation.alpaco.email/template/input-groups/input-types/textarea.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.