A layout change has two steps: Save layout records it in the project model; Generate updates the application files. Neither action deploys a release by itself.
Apply the layout to your application
- Finish arranging the entity in Admin editor.
- Resolve any validation messages: duplicate placements, unavailable fields, missing titles or rows wider than 12 columns cannot be saved.
- Click Save layout.
- Open Generate, review the plan and diff, then generate the application.
- Open the generated admin and check its form. Update or deploy the application through your usual release workflow when ready.
Saving a layout does not create database columns, run SQL migrations, start an AI request or deploy your application. Field definitions, validation and access still come from Content.
Undo, Reset and leaving a draft
| Action | What it does |
|---|---|
| Undo / Redo | Move through edits in the current layout draft |
| Reset | Restore the Content field order and existing headings/dividers as the draft |
| Save layout | Save the draft to the project model |
| Discard draft | Leave without saving the current draft |
Reset is not permanent until you save it, and you can undo it before saving. When leaving with unsaved changes, choose Keep editing, Discard draft or Save and leave. This is layout draft handling, not database backup or generation-history rollback.
If Content changes in another window, the editor marks the layout as stale and asks you to reload before saving. Do not expect an older draft to overwrite the newer model. If you choose Reload layout, review the warning about discarding the current draft first.
Fields added or changed later
New fields that have no explicit placement still appear in Other fields. Renaming a field updates its layout reference; removing or hiding a field removes its placement. These maintenance changes do not require an active editor subscription. To intentionally redesign the saved layout, editor access is required.
Work with custom zones
Generated form layout and custom behavior can evolve in parallel. Keep your hooks, components and complete custom pages in the supported custom zones; do not edit generator-owned output to implement a layout change. Preview shows built-in controls; custom components render in the generated admin.
An already saved layout can still be generated without an active editor subscription, and the generated admin runs independently of your Admingen account. See admin customization and generation and recovery.