Appearance
Pages & navigation
A project can hold many pages, and you link between them so visitors can move around your site. This page explains the multi-page model, how to link pages from buttons and text, and the public URL each page lives at.
Pages inside a project
Each page you design is a file in a project. A project might have a home page, an about page, a contact page, and a pricing page — each an independent FormDocument with its own sections, theme overlay, and settings. You switch between them in the workspace, and they publish independently.
Every page has page settings:
| Setting | What it controls |
|---|---|
title | The page name — also the browser tab title and the basis for its slug |
description | Meta description for search engines and social shares — see SEO |
visibility | public (default) or private — private pages require a signed-in member |
background | An optional page-wide background painted behind every section |
| on-submit flow | An optional flow to run with the data when a form on the page is submitted |
Linking between pages
Two components can navigate: Link (clickable text) and Button. Both expose a Link to field that understands your project's pages, so you don't paste raw paths — you pick the destination page and FlowRunner wires up the correct URL.
- On a Link, set the
href/ Link to field to a page in the project. - On a Button, set the
href/ Link to field the same way — a button with a destination navigates instead of submitting.
A typical pattern: drop the Header block on every page and point its nav Links at your other pages, and point your Hero and CTA buttons at the page you want visitors to reach next.
TIP
Use the Link to picker rather than typing a URL. If a page's slug changes later, links chosen through the picker keep pointing at the right page.
Public URLs
When you publish, each page is served at a stable, shareable URL built from the project id and the page's file id:
text
https://<your-host>/p/<project>/<file>The top bar gives you three ways to work with this URL:
- Publish — pushes the current version live, so the public URL serves what you just built.
- Share — copies the public link to your clipboard.
- Open — opens the live public page in a new tab.
NOTE
Publishing is explicit. Edits autosave as you work, but the public page keeps serving the last published version until you press Publish again — so you can keep editing without your changes going live prematurely.
Custom domains
The /p/<project>/<file> URL always works, but you don't have to ship it. Connect your own domain and verify it with DNS, and your pages serve from your brand's address instead. See Custom domains for the setup.