> For the complete documentation index, see [llms.txt](https://docs.realmacsoftware.com/elements-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.realmacsoftware.com/elements-docs/using-elements/editor/page-manager.md). # Page Manager Manage the structure of your website Easily manage the structure of your website. Create pages and folders and drag to re-arrange them just like you would in the Finder. {% embed url="" %} ### Pages To create a new page, press Command-N or use the "+" symbol to the right of the Pages title. {% hint style="info" %} To add other file types or folders, right-click inside the page list. {% endhint %} ### Code Files (html, css, js, etc) To create a file in your project, right-click in the Page Manager and choose **New File**. ### Links Add links to your site structure. To Create a link page, right-click in the Pages area and select "New Link" from the menu. ### Markdown Files To create a Markdown file with optional front matter, right-click in the Page Manager and choose **New Markdown File**. ### Folders Folders are a useful way to organise site content when you don’t need a top-level page. They can contain any number of pages or additional folders. To create a folder, right-click in the Pages area and select **New Folder** from the menu. --- # 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://docs.realmacsoftware.com/elements-docs/using-elements/editor/page-manager.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.