Visual Schema Editor

Data structure and presentation are deeply connected. A new field you add to your data model should immediately be available in forms, list views, and detail panels. But in many platforms, changing the data model and updating the UI are separate operations in separate tools. You define the schema somewhere, then separately update the display somewhere else.

The visual schema editor brings data structure definition into the builder — the same tool you use to configure pages and components.

Add Fields Without Leaving the Builder

Select any object type in the builder and open the schema editor panel. The current field list is displayed with its types and settings. Click "Add Field" to open the field creation form:

• Enter a field name and display label
• Select the field type: text, number, date, boolean, select, relation, file, or structure
• Configure type-specific settings: required flag, default value, option list for select fields, related object for relation fields
• Set display hints: field width, help text, whether to show in list views by default

Save, and the field is immediately available across the application. It appears in the field picker when configuring columns, forms, and detail panels.

Edit Existing Fields

Clicking any existing field in the schema editor opens its configuration. Update the label, add or modify options for a select field, change the required setting, adjust the default value. The change applies immediately across all views that display this field.

Field type changes are handled carefully — some type changes are non-destructive (a text field can expand to accept longer values), while type changes that could affect existing data are flagged for confirmation.

Structural Fields and Collections

The schema editor supports complex field types: structures (groups of sub-fields) and collections (repeating groups). Creating a structure field opens a nested field editor where you define the sub-fields. Collections use the same pattern.

These types appear appropriately in forms as structured sub-forms or repeater sections, without any additional configuration.

The Feedback Loop

The most significant benefit of the visual schema editor is the compressed feedback loop. Think of a field you need, add it in the schema editor, see it available in the form immediately, add it to the list view, refresh the page. The cycle from "I need this field" to "I'm working with it" takes minutes.

This speed encourages iteration. Try a field, see how it works in practice, refine the name or the type. Data model design becomes exploratory rather than consequential.