> For the complete documentation index, see [llms.txt](https://documentation.alpaco.email/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.alpaco.email/template/input-groups/input-types/boolean.md).
# Boolean
A simple on/off or true/false input, displayed as a switch in the **Email Editor**.
Works great for:
* **Show/hide** specific elements, i.e. making a CTA button optional.
* **Toggle direction**, i.e. in a component showing an image on the left, and a text on the right, you can make a toggle to allow the marketeer to switch the direction, so text shows on the left and image on the right.
### Template Editor
This is how it looks in the Template Editor
This is how it can be applied in the code. Notice the {% if statement %} wrapping around the TD's
Notice how with **Boolean** we can wrap other code bits into a Liquid statement like so:
```liquid
{% if my_input_group_name.my_text_align %}
{% else %}
{% endif %}
```
### Email Editor
This is how it looks in the Email Editor
---
# 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://documentation.alpaco.email/template/input-groups/input-types/boolean.md?ask=&goal=
```
`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.