> For the complete documentation index, see [llms.txt](https://storypress.gitbook.io/storypress-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://storypress.gitbook.io/storypress-docs/content-blocks/faq.md).

# FAQ

The **FAQ** block shows a list of questions and answers that visitors can expand and collapse (accordion style).

***

## What you can do

* Add multiple **FAQ items**, each with a question and answer.
* Use a single **FAQ** block for one Q\&A, or an **FAQs** block to group several **FAQ** blocks.
* Optionally add a **heading** and **background** to the section.

***

## How it works

* **FAQ** — One question/answer pair. You fill in the question and the answer (often rich text).
* **FAQs** — Container for multiple FAQ blocks. Add several **FAQ** blocks inside it to build the full list.

Visitors see the questions by default; clicking a question expands or collapses its answer.

***

## Tips

* Keep questions short and answers scannable (bullets or short paragraphs).
* Use the **FAQs** block when you have more than one item so the whole section is grouped.


---

# 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://storypress.gitbook.io/storypress-docs/content-blocks/faq.md?ask=<question>&goal=<endgoal>
```

`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.