> For the complete documentation index, see [llms.txt](https://docs.realmacsoftware.com/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/classic/user-manual/project-window.md).

# Project Window

Finding your way around the main window in RapidWeaver

This is a quick visual guide to finding your way around the RapidWeaver interface.

![](https://3941723260-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQxK7JyV6iH6ddgHOOt8v%2Fuploads%2Fis4TsMzVvNVcewHnbiyv%2F595e6410-3417-49f5-afac-5b2192199d91.png?alt=media\&token=13f1aabc-9381-499c-9832-c27d7951400a)

Any page that you add to your RapidWeaver project appears in the Page List, and the navigation menu for your website is based on the layout of the pages in the Page List.\
\
You can drag and drop pages to re-order or drag pages onto other pages to create a nested page. You can also re-order the different groups (Pages and Settings) in the Page List.\
\
You’ll also notice a blue dot appearing to the right of each page: this signifies that there are changes that have yet to be published. When the changes to each page are published, the blue dot is hidden.\
\
Right-clicking on a page in the Page List displays a contextual menu with some useful options, including Duplicate a page or Mark As Unchanged (and the blue dot for the page will disappear).\
\
Just like in other apps, you can edit the name of any Page List item by double-clicking it.\
\
The Page Inspector is where you can change settings relating to the selected page, and change the browser title or the file name of the page.\
\
Give each page you add to your site a proper name. The filename should usually be index.html, while the folder name should be descriptive, for example;

```
/about-us 
```

would be

```
mycompany.com/about-us/index.html
```


---

# 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/classic/user-manual/project-window.md?ask=<question>&goal=<user_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.