# Understanding pages and their types

A page is the canvas on which the user interface of the application is built. We build the user interface by placing various components on the page.

## Viewing the existing pages:

1. In the **Navigation menu**, under the **Developer** role, in the **Developer** group, click **Pages**. The list of all existing pages is displayed.

![List of existing pages](https://1117313960-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LzMJAXNyRSI4WE3Jt4z%2F-M2IeydQ9fT4EgGrMzGA%2F-M2IfUoqXbGVhVm-pbb2%2FList%20of%20pages.png?alt=media\&token=5681c5b4-812b-4e2c-be28-f60909647841)

{% hint style="info" %}
Note

To open the page canvas and design the user interface, click the required page URL.
{% endhint %}

## Understanding the types of pages

| **Page type** | **Description**                                                                                                                                                            |
| ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Abstract**  | <p>These pages can be used as pre-defined template pages and to shelter multiple child pages.</p><p><em>You cannot edit the abstract pages through its leaf page.</em></p> |
| **Extension** | These pages can be used as a component in different user interfaces throughout the application.                                                                            |


---

# Agent Instructions: 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:

```
GET https://docs.cloudio.io/creating-pages/working-with-pages/understanding-pages-and-their-types.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.