> For the complete documentation index, see [llms.txt](https://docs.zingy.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zingy.ai/app-editor/pages-and-forms/create-a-page.md).
# Create a Page
In the App Editor, go to the **`Pages & Forms`** tab and use the :heavy\_plus\_sign:**`New`** icon to add a new page to your App.
Zingy App Editor - New Page button
Select **Page** as the type and provide a unique ID for your page.
{% hint style="warning" %}
Please note that the **ID of your page cannot be changed**, but you can change the display name for the page.
The ID is used internally to refer to the page. The ID also gets used as the default name in the page's URL when you publish the page. You are allowed to change the name in the page's URL. See [Page Publishing](/app-editor/page-settings.md#publishing) for more information.
{% endhint %}
Once the App editor creates your page, it will be shown amongst the list of pages.
Zingy App Editor - Page list
See [Adding Page Content](/app-editor/page-editor/adding-page-content.md) for information about designing your page.
---
# 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.zingy.ai/app-editor/pages-and-forms/create-a-page.md?ask=&goal=
```
`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.