> For the complete documentation index, see [llms.txt](https://docs.eximee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/formularze/tworzenie-formularza/edycja-stron.md).
# Editing pages
## Introduction
As part of form design in **Eximee Designer** the user has the ability to edit individual **application pages**, which make up its logical and visual structure.\
Each page may contain [base components](/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/formularze/praca-z-komponentami-bazowymi/dodawanie-i-parametryzowanie-komponentow.md) or complex ones, and its behavior and appearance can be modified in the page properties panel.
## Form structure and pages
A form in Eximee consists of **steps** and **pages**. Page management is done in **the Steps tab**, while their content and layout are modified in the **Application tab**.
## Visibility conditions
Visibility conditions allow control over whether a given page will be displayed to the user.\
They are defined in the tab **Request** on the selected page, in the section **Data quality** (field **Add visibility condition**) using logical expressions created in the **advanced condition editor**, which allows referencing form field values or session variables.
Visibility conditions can also be defined in the **Steps** tab **Add condition**– through the option
, which allows defining the presentation logic of individual form steps.
## Page layout editing
Each page has a defined column layout, determined when the form is created.\
Changing the number of columns (**numColumns**) is possible only by editing the XML code in the **Source**.
{% code title="Example of a page fragment with the number of columns set to 12" %}
```xml
```
{% endcode %}
{% hint style="info" %}
**Note:**\
Before reducing the number of columns, adjust the width of the components (`horizontalSpan`) - their sum in a row must not exceed the number of page columns.
{% endhint %}
## Page styling
Each page can have its own CSS styles assigned.\
The style defines the visual presentation of the page (e.g. layout, margins, background color). The defined style can be set in the panel **Properties** (section **Styling**) or directly in the XML source via the attribute `styleName`.
Properties `fixedColumns` and `styleName` allow defining the page appearance - namely the layout structure and the assigned CSS style.
It is recommended to use platform styles consistent with the implemented visual theme.\
More information: *Form and component styles*.
## Page properties
After clicking an empty area of the application editor, the panel opens **Properties** of the page.
Figure 1. Fragment of the page's "Properties" panel
> More information about page properties [here](/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/formularze/tworzenie-formularza/kroki-i-strony-formularza.md#wlasciwosci-stron)
## Best practices
* Establish a consistent page naming convention (e.g. *Page1*, *Page2*, *Summary*).
* Use visibility conditions only where necessary.
* Establish a uniform number of columns across all form pages.
* Design the component layout so that their sum `horizontalSpan` in a row does not exceed the number of page columns. When changing the number of columns, remember to adjust the component widths.
* Pages located after [the save point](/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/formularze/tworzenie-formularza/punkt-zapisu-wniosku-i-mechanizm-ostatnich-stron.md) are treated as **end pages** (e.g. thank-you, confirmation)
## FAQ
**Can the order of pages in the form be changed?**\
Yes. In the **Steps** tab, pages can be dragged using *drag & drop*. Changes are saved automatically.
**How do you hide a page from the user?**\
In the page properties panel, set the **visibility condition** (`visibleCondition`). The page will be shown only if the condition returns the value `true`.
**Can the number of columns on a page differ from the rest of the form?**\
Yes, but only by editing the XML source in the **Source** - by changing the attribute `numColumns` in the element ``.
**How do you set a page as a thank-you page?**\
Simply place it after [**The form save point**](/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/formularze/tworzenie-formularza/punkt-zapisu-wniosku-i-mechanizm-ostatnich-stron.md) - the system will automatically treat it as an end page.
---
# 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.eximee.com/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/formularze/tworzenie-formularza/edycja-stron.md?ask=&goal=
```
`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.