Creating Pages, Portals & APIs

Project Branches

Your project is divided into three branches, each with its own root (public, private, tools) that serve different purposes - but are not entirely exclusive. You can add pages to the public and private branches, but any pages added to the private branch will be locked behind a login screen and require authentication.

⁠

Adding Pages

In various places you will see a small + icon indicating you can add pages there. The branch and position you choose to add a page will dictate whether it’s public, private and what data is available on the page (if its on a dynamic path).

⁠

Normal Pages

These are just content pages without a connection to a specific record, added mostly at the top levels of your branches. They can still be dynamic, if they are on a dynamic path, and display dynamic content using actions and queries, but the page itself does not connect to a data source.

Dynamic Pages

A dynamic page is like a template where you build a design using variables, and can then see a variation of the page for every record in its data source. They can be connected to each other to create dynamic paths, where each level in the path represents a record from a specific table. If a dynamic page has a parent, you will be asked if you want to connect to parent. This will automatically add a list of the dynamic pages to the parent so users can navigate to them.

⁠

⁠

Preview Dynamic Path in the Editor

When opening pages with dynamic paths in the editor, you will be prompted to choose which dynamic path (records) to work with. While making these selections if a relationship filter is applied you will see it being applied to the list of available records. Once you have chosen all the required values to simulate a user having navigated to the current page, you can begin building the content.

⁠

⁠

Index Pages

When adding dynamic pages at the top level of your projects, you may be asked if you want to add an new page (create an index) above it. An index page is a special page type that will appear on the same path as the dynamic page, when the dynamic value is missing. For example, the index page for /products/nike would be /products. They exist just to help users and search engines find your dynamic pages.

Index pages are always paired with dynamic pages, at the top level of a project.

⁠

⁠

Editing Pages

You can access page settings by clicking on the page, or open it in the editor by clicking the Open in Editor button.

⁠

⁠

Private / Portals

Any pages added to this branch can access the user record and display their data, or use it in queries and conditions to create dynamic interfaces.

Tools / API

The tools branch can be used to create API endpoints and tools that are accessed directly from external system such as Airtable to fetch dynamically rendered content that is not a page or portal. Examples are email (html) to be used in automation systems.