Open Orbit

Block library

Understand the components you can use on an Orbit page, how they connect to data, and when to use a recipe instead.

Orbit's block library provides the components you arrange on app pages, such as forms, lists, tables, charts, and calendars.

The components in Mockup are the same components your live app uses. You compose a page from those parts rather than draw a separate prototype.

What you can put on a page

The Mockup product page lists these component types:

  • Forms and buttons for input and actions.
  • Lists and tables for records.
  • Charts and calendars for different views of information.
  • Date pickers, dialogs, and tabs for page interactions.

These are examples, not a complete catalog. The right component depends on the information or action the reader needs.

Components, data, and appearance are separate choices

A list's appearance does not determine which records it shows. A list connected to a table displays records from that table.

The inspector controls component size, spacing, and colour. A shared theme controls colours and type across pages. You do not need to write CSS.

For example, consider a repair request app with a requests table. The names in this example are yours to change:

Page partPurpose
A list connected to requestsShow the stored repair requests
A formLet a person enter a repair request
A buttonGive the person an action to take

The presence of a form or button does not prove that a submission saves a record. The action needs a check in the app, separate from the component's appearance.

Read Entities and records for the difference between stored records and their structure.

A block is not a recipe

A component is a part of a page. A recipe supplies a prepared section or page that you can adapt.

Individual components suit a change to one part. A recipe can suit a section or page when its layout already fits your needs.

Appearance and saved records need separate checks

In the repair request example, the list's appearance and the form's save behaviour need separate checks. A form that looks correct does not establish that requests are saved.

Use Edit a mockup for page changes. Before people rely on the result, test the app before launch.