> 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/core-concepts/formsort-quickstart-guides/add-informational-content.md).
# Add informational content
Add text, photos, and videos to your flow.
Not all of the content you add to your flow needs to be questions you are asking the responder! You also may want to add text or pictures to your flow that are **purely for informational purposes**. Sometimes this is to educate the responder about what you offer, or to provide more information about why they are disqualified from your service.
See the types of informational content you can choose from when you click "**Add Question**" and scroll below "**Content**".
## Common types of informational content:
### Add text and pictures to your steps
You can add add text and pictures before, between, or after the questions you are asking.
### Welcome page
### **Educational steps**
Share facts or statistics that are relevant to your product or service to encourage the responder to continue the flow.
### Transition steps
Tell a responder in the middle of the flow what's about to happen next.
---
# 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/core-concepts/formsort-quickstart-guides/add-informational-content.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.
