# Page Designer

> Build visual pages and forms over your data sources.

## What is this for?

The Page Designer lets you build your own screens and forms on top of your record types and selected ready-made data lists. You build a page from blocks such as a list table, form, detail card, filter, button, text and tabs, much like placing ready parts side by side. You design the screens your team uses every day without writing code.

**Pages** and **forms** work together. A page is a layout of blocks. A form is reusable: design it once, use it on several pages, and when you update it, every page that uses it updates too. Screens respond to each other: when a row is selected in a list, the connected detail card or form instantly shows that record. Your design is edited as a draft and goes live only when you publish it.

## Example scenario

At a facility management company, field coordinator Deniz wants to track maintenance requests on one screen. She builds a page with a list of "Maintenance Request" records on the left and the selected request's detail card on the right. The list shows only the subject and priority. She connects the list to the detail card, so clicking a request shows its details immediately. She publishes the page, and her team opens it from the menu to see the requests open to them.

## Who uses it

- **Screen designers:** People who design, publish and add screens and forms for their team to the menu.
- **Process owners:** People who want a tidy screen for one workflow, such as a "customer detail page" or an "order entry form".
- **Team members:** People who open published pages from the menu and do their daily work. They see only the data they are allowed to see.

## Step by step

1. **Create a new page.** In the Pages section, start a new page and give it a name.
2. **Place blocks.** In your section, row and column layout, add a list table, detail card, form, filter, or text and buttons.
3. **Choose a data source.** For each data block, choose one of your record types or a ready-made data list that can only be viewed (projects, tasks, members). Pick which columns appear.
4. **Connect the blocks.** Connect the detail card or form that should update to the list. This makes the screen respond to selection.
5. **Design forms.** Design the forms you plan to reuse: choose fields, set their order and labels, then place them on your pages.
6. **Publish.** When the design is ready, publish it. Users can then open the page, it can appear in the menu, and it can be shared with a readable address. Draft edits stay hidden from users.

## Process flow

```mermaid
flowchart TD
    A[Create a new page] --> B[Place blocks list form detail]
    B --> C[Choose a data source]
    C --> D[Connect blocks]
    D --> E[Edit on the draft]
    E --> F{Ready to publish}
    F -- No --> E
    F -- Yes --> G[Publish and show in menu]
    G --> H[Users work with data they are allowed to see]
```

## Frequently asked questions

**Do I need to know how to code to build a page?**
No. You build pages from ready blocks: list, form, detail, filter, text and button. Add each block, connect it to a data source and set its layout in the visual editor.

**What is the difference between a page and a form?**
A page is the screen where blocks come together. A form is reusable: design it once and add it to many pages. When you update the form, every page using it updates automatically.

**Does everything I design go live right away?**
No. Design happens on a draft. It goes live only when you publish, and users never see drafts.

**What data can pages show?**
They can show your own record types and read-only ready-made lists (projects, tasks, members). These lists are for viewing only, and they do not include sensitive personal information.

**Can I update another block when a row is selected?**
Yes. Connect a list to a detail card or form. When a user selects a row, the connected block shows that record's information instantly.

**How do users reach a published page?**
A published page can appear in the menu automatically and opens with a readable address. Each user sees only the data they are authorized to see.