> For the complete documentation index, see [llms.txt](https://mpithemes.gitbook.io/shella-shopify-theme/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mpithemes.gitbook.io/shella-shopify-theme/home-page-sections/faqs.md).

# FAQs

{% hint style="info" %}
**Add section -> FAQs**
{% endhint %}

 Here you can add sections for each FAQ and decide how to represent its answer, either as a page or as a text, which you will write manually. Let’s take a look at this section.\
&#x20;In the **“Question”** field, you can write a question to which you will provide the answer. You can select a page in the **“Page content for the answer”**. If no page is selected, the default page “Include FAQs Answer” will be used. How to add and edit a page you can find [<mark style="color:blue;">**here**</mark>](https://mpithemes.gitbook.io/shella-shopify-theme/get-started/how-to-add-and-edit-a-page). You may use the field **“Answer”** to write the answer manually. If you want your FAQ answer to be shown as open, you can enable the **“Is open”** option.

&#x20;In our example, we have added 2 “Section” blocks, and this is what we have got:

![](/files/-MguMPZrLmBKkZ1-7aYG)


---

# 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://mpithemes.gitbook.io/shella-shopify-theme/home-page-sections/faqs.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.