> For the complete documentation index, see [llms.txt](https://docs.kasko.io/webapp-builder-manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kasko.io/webapp-builder-manual/basic-concepts/pages.md).

# Pages

### What are pages?

Every webapp consists of multiple pages. Each page contains some information and/or input fields, that user would be able to fill. This is a good way to split questions into groups so that users that are going trough the flow doesn't feel overwhelmed.

To create new page just click "Add new page" button and enter a name, it CAN contain any characters and spaces.

<figure><img src="/files/4g7oMjZZY9FwkhqkJq6v" alt=""><figcaption></figcaption></figure>

Pages can be reordered using drag & drop. This will be the order what will be exported in manifest.

#### Next page logic

It is possible to have logic that determines what screen user should be sent to after pressing "next" button.

<figure><img src="/files/Tv2Ef4UB7e92gTD0S9wX" alt=""><figcaption></figcaption></figure>

It can contain one or multiple conditions that compares user entered data to some value.

{% hint style="info" %}
For example: if `data.duration` is `"p3y"` then user will be sent to `Knockout` page, otherwise `Details` page.
{% endhint %}

<figure><img src="/files/DlEiIEDSgFCNLMIXMyiI" alt=""><figcaption></figcaption></figure>

If there's a need for multiple conditions, all of them will be executed one by one, starting from the top. Whenever one of the conditions pass, user will be sent to the page that is defined in that particular condition.

Data from different pages can also be used for building this logic.
