> For the complete documentation index, see [llms.txt](https://docs.cremawork.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cremawork.com/v-3/overview/folder-structure/page.md).

# page

All the code related to the dashboard, apps, and other pages lies in this folder. We have kept the folder structure very simple and easy to understand by breaking the folders into sub-folders and following proper naming. For example, the modules folder contains a folder named 'dashboard' which contains all the files related to the dashboard, similarly, a folder named 'apps' contains all the code related to apps included in the template.<br>

![page directory of the crema](/files/k9mDjcRzY2eotbKfJVSI)

{% hint style="info" %}
In  the nextjs page directory will be move into <mark style="background-color:blue;">modules</mark>**.**  <mark style="color:blue;">page</mark> is the default directory in the nextjs.
{% endhint %}


---

# 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.cremawork.com/v-3/overview/folder-structure/page.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.