> For the complete documentation index, see [llms.txt](https://knowledge-base.letsgetdigital.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge-base.letsgetdigital.com/the-admin-panel/content/application-1/pages.md).
# Pages (App)
For any information you want to add to the app where there isn't a dedicated facility for this, you can create customised pages. This article explains the functions of pages and how to set these up.
## Managing pages
### Creating a page
1. Open the home page.
2. Click on 'New page'.
3. Complete the page detail fields as they're described (Any field indicated with a \* is mandatory).
4\. Click on ''Add page''.
### Editing and deleting a page
Each page has three icons to its right (Under actions):
**Edit icon:** Click here to make adjustments similar to when first creating a page. **Here you can add the main text of the page!**
**FAQ icon:** Click here to add **FAQs with answers in the form of bullet points.** \
 Delete icon: Click here to remove the page altogether.
## Integration
Follow the instructions in the navigation article here to find out how to add this (and other features) to your app!
## The result
---
# 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://knowledge-base.letsgetdigital.com/the-admin-panel/content/application-1/pages.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.