What are pages
A Page is a freely composed interface. You build it out of Blocks: headings, text paragraphs, images, input fields, embedded views, evaluations, and layout containers.
Publishing a Page creates a Portal — an independent web address you can share or embed in your own website.
The empty state in the Pages area describes it like this:
Welcome to your "Pages" area. Here you can keep all your information, notes, and documentation.
But that only covers the simplest case. Pages can do a lot more.
What Pages are good for
| Use | What you need for it |
|---|---|
| Internal documentation, notes, manuals | Text and heading blocks |
| Dashboard with metrics | Counter, sum card, donut chart |
| Customer portal with a data overview | Embedded Grid view |
| Custom-built data entry screen | Form field blocks |
| Landing page for a process | Button or QR code block linking to a Flow |
| Interface within a Flow | A Page that a Flow step displays |
Page, form, or view?
Three tools that overlap. The rule of thumb:
| You want to … | Use |
|---|---|
| Collect data, quickly and without design effort | Form |
| Display and edit data, in a table | View |
| Combine several things: text, data, input, evaluation | Page |
| An interface with its own structure and layout | Page |
A Page can replace a form
Pages have the same input fields as forms — plus layout, text, images, and embedded data. When a form hits its design limits, a Page is the next step.
For simple data collection, a form is still faster: pick fields, share, done.
Pages and Blocks
A Page is a tree of Blocks. Blocks can contain other Blocks — a Layout block arranges the Blocks it contains side by side or stacked, and a Tab layout shows sub-pages as tabs.
The Block picker is grouped into three categories:
- Basic Blocks — Paragraph, Headings, Image, Sub-page, Layouts
- Special Blocks — embedded views, evaluations, buttons, HTML
- Form field Blocks — all input fields
→ Block overview · Block types reference
Sub-pages
A Page can contain sub-pages. That's how you build multi-level structures — a manual with chapters, a Portal with several sections.
Two Layout blocks display sub-pages in particular:
- Tab layout — Show sub-pages as tabs
- Stepper layout — Show sub-pages as steps
The Stepper layout is suited to guided processes: users work through it step by step.
The two modes of a Page
| Mode | Purpose |
|---|---|
| Editor | Editing. You see block frames and controls. |
| Application | Preview. You see the Page as visitors see it. |
Back to editing takes you back from the preview.
"Page" has three meanings
Watch closely when reading the interface which one it means:
- Page (Portal) — what this chapter is about.
- Form page — a section within a multi-page form.
- Flow page — a Page displayed by a Flow. Technically this is a Page in the sense of 1, embedded in a workflow.
Two Flow steps are also both called Show page — one is a trigger, one is an action.
From draft to Portal
A Page is initially only visible internally. Only Create portal link makes it reachable from outside.
That's also true for the preview: if you want to view the Page as a Portal, ApptiveGrid asks:
Viewing this preview as a Portal requires a published Portal link. Would you like to create one now?
Where Pages live
Pages belong to a Space and appear in the sidebar under Pages. Whether this area sits above or below the Grids is set in the Space settings.