Use preview to check the form before generating it. It helps you assess widths, grouping and the order of controls; it is not a running copy of your application.
Check the layout
- In Admin editor, select the entity and open Preview.
- Choose Desktop to check the column layout.
- Choose Mobile to check the narrow arrangement. Form columns stack vertically on mobile.
- Visit every form tab. Check that headings and descriptions explain the following fields.
- Return to Arrange to change a placement, then save and generate.
Preview renders the built-in controls. It shows field types, required markers and upload areas, but it does not submit real records or execute custom components. Check custom behavior in the generated application.
One layout for all languages
Content languages are configured in Content → entity → Languages, not in Admin editor. The form layout is shared across the entity's languages. There is no locale switch in Admin editor.
For example, ENTITY_NAME can have translated name and description, while sku and price are shared. Arrange each field once. In the generated admin, language tabs switch translated values while shared fields remain the same. The default content language is first in the language tabs.
After generating, open the real ENTITY_NAME form and check each language, including long translations. If validation finds an error in a translated field or an inactive form tab, the generated form reveals the corresponding language/tab before focusing the field.
See Content / Languages for selecting languages, translated fields and required translations.
What still needs a real application check
| Check | Where |
|---|---|
| Field widths and grouping with built-in controls | Admin editor preview |
| Entering and saving translated values | Generated admin |
| Custom field components and business behavior | Generated admin |
| Access to entity pages and related data | Generated admin, with the intended user role |
Layout settings do not change field validation, translation requirements or permissions.
Layout preview and Branding preview
Admin editor preview checks placement and built-in controls. Project settings → Branding separately previews Content and Login appearance for the light/dark drafts. Neither preview executes custom components, signs in or saves real records. After Save and Generate, check long translations, field help and keyboard focus on the generated form with the intended palette and user role.