Site ↗
Documentation sections
UI interface · 0.8.1

Content: modules, entities and fields

Organize the application model, find entities and save changes before generation.

On this page

Content overview

Build the application model in Content. Select a module/entity on the left; fields/actions appear on the right. Settings open in a side panel. This does not create application records; use the generated admin for those.

Navigation and search

Enter a name/label in Find module or entity to locate model objects, not application records. A module arrow collapses its entities; its title opens settings. Virtual entities have a badge.

Selecting an entity opens Fields. Click a field row to configure it; delete/expand icons act separately. Required, Primary key, Searchable, Filterable and Sortable badges expose properties immediately.

Modules

Create a module before adding entities. It groups entities in the UI and forms part of API addresses.

Field Example Purpose
Module name site-data Technical name: lowercase letters, digits and hyphens; starts with a letter
Module title Контент сайта Menu label; empty values use the technical name

Create module creates it; Save module saves edits. Settings list its entities with links. Move up / Move down changes module order; save/discard drafts first. Delete module requires an empty module: move entities first. Changing a nonempty module's technical Module name requires impact confirmation. Label edits do not change API addresses. Move entities in entity settings; their API acquires the new module prefix.

Saving changes

  1. Open creation/settings.
  2. Complete Basic settings and, if needed, Advanced settings / Access.
  3. Finish; the projection field selector uses Save fields.
  4. Wait for save confirmation and model refresh.
  5. Go to Generate to apply file changes.

Tab switching retains values. Finish saves; Cancel/close does not. Unsaved changes trigger draft handling. After concurrent changes, refresh and compare: stale forms must not overwrite another person's work.

For an interrupted connection and unknown write result, use the offered Refresh. Check what saved before repeating to avoid duplicates.

Recommended design order

For a catalog, create catalog, Category/Product and their identifiers. Add regular fields, then Product → Category. Configure access afterwards. Add a virtual entity if the website needs a distinct response shape. Finish with Preview/Generate.

Details: entities, fields, access, relationships, virtual entities.

CLI can edit the same model. Do not manually change application structure in generated files; use the model.