> 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/adding-questions-and-content/content-reference/statement.md).
# Statement
Displays content that does not require an answer from the responder.
Using a **Statement** component type, you can add any image, video or text. This is commonly used for explanation of concepts or as breaks in between various sections of your flow.
## Styling text
Like in any other component, you can use [markdown](/styling/customizing-appearance/typography.md#markdown-styling-support) to change the font properties of the Statement text.
You can also change the alignment of the component block by enabling **Text alignment override** to override the default alignment setting.
### Images and video
To add images and videos, you can enable **Has image or video** toggle and use the **positioning** and **image style** menus to position and size the content appropriately.
#### Positioning
**Top, Right, Bottom, Left, Center** are all valid keywords for background image positions - the image will be placed in the respective position within the element, which can differ between the X and Y axis.
### Adding links
You can also use informational content to embed links. The default setting opens the links in a new tab for the responder. By enabling **open links inline**, you can ensure that the links are opened in the same tab.
### Collapsible content
By enabling **Is collapsible?**, you can have content that expands and collapses, which can show or hide more details when the responder clicks on the header. You can change the default behavior to collapsed or expanded.
---
# 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/adding-questions-and-content/content-reference/statement.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.
