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

# Setting up FAQs

Let's get some terminology and definitions out of the way.

* The Pakk entity name is *FAQ*.
* An FAQ consists of a list of *questions* and *answers*.
* The questions and answers in an FAQ should be related to each other, i.e. they should be on the same theme or subject.&#x20;
* An FAQ can also be given a title, subtitle, SEO meta, image etc.
* You can create as many FAQs as need.
* FAQs are "webable" entities, meaning that to show an FAQ on your site, you need to *web enable* it, assign it to the sites on which you want it to appear and give it a slug (url path component).

So essentially an FAQ page is much like a regular page, but with the addition of an *enforced structure* for the content. The FAQ page consists of a list of *questions* and *anwers*. The list can be as long as you want, and you can add, remove and edit at any time. In fact, you should consider each FAQ a living document that soaks up and centralises knowledge over time.

#### Questions <a href="#questions" id="questions"></a>

Are literally just a sentence of text. No styling, no links, nothing fancy.

#### Answers <a href="#answers" id="answers"></a>

Are a chunk of text, but with *markdown* formatting, so you can add a bit of pizazz to your answers if you want, including images, links, bold, bullet lists etc.


---

# 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://docs.pakk.io/websites/content/faqs/setting-up-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.
