> For the complete documentation index, see [llms.txt](https://docs.formsort.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.formsort.com/styling/customizing-appearance/question-containers.md).
# Question containers
Questions can have an overlay on top of the default styles applied to them, which gives the user a degree of freedom in defining how different questions and content components can appear on the page.
Any theme provided by Formsort will have at least one container style - default - but you can build up your collection of different styles by heading to **Containers** in the Theme editor.
**+Add question style** allows you to create a new question container.
{% hint style="info" %}
The **Label margin** is of particular note here, since it provides spacing between the Question label the buttons/input bars related to it.
{% endhint %}
Once a container style is defined, any question can use any of the container styles by clicking the question, and choosing the container style in the **Question container style** dropdown in the Style menu.
These containers are helpful to make different kinds of questions visually distinct: a common pattern is to create an **optional** question class that is used for optional questions, with left border and margin to differentiate it from non-conditional questions.
---
# 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.formsort.com/styling/customizing-appearance/question-containers.md?ask=&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.
