ENTITY_NAME denotes your entity directory or filename; EntityName denotes its generated code type or export-name prefix. Use the actual names in your project. FIELD_NAME denotes a field name. These are placeholders, not required entities or literal files.
Everything related to EntityName belongs to one feature: types, columns, form, pages and custom extensions. Shared mechanisms live in shared; app assembles entity interfaces into the admin application.
Changing one cell or form control does not require replacing the whole page. Other standard parts continue to update from the model.
The tree shows main paths using EntityName as an example, not a complete inventory. Files depend on the model and project capabilities.
admin/src/ — EntityName CRUD example
src/
├── main.tsx
├── App.tsx
├── app/
│ ├── providers.tsx
│ ├── router.tsx
│ ├── menu.ts
│ ├── layout.tsx
│ └── theme.ts
├── features/ENTITY_NAME/
│ ├── generated/
│ │ ├── model.ts
│ │ ├── schema.ts
│ │ ├── columns.tsx
│ │ ├── form.tsx
│ │ ├── list-page.tsx
│ │ ├── edit-page.tsx
│ │ ├── routes.tsx
│ │ └── ui-extension.tsx
│ └── custom/
│ ├── extension.tsx
│ └── ui-extension.tsx
└── shared/
├── api/
│ ├── client.ts
│ └── generated/client.ts
├── forms/field-controls.tsx
└── list-state.tsx
app — UI assembly
Providers, layout, theme, menu and routes connect entity interfaces. This is where shared mechanisms are wired; an individual feature does not need to know the whole application structure.
features — an entity interface
EntityName types, schema, columns, form and pages sit alongside their extensions. When the entity changes, related code stays in one feature rather than being scattered across general form and table folders.
shared — reusable mechanisms
HTTP clients, form controls, list state and media support are reused. Generated forms follow common loading, validation and saving rules. Custom components placed in supported slots must follow the same contract.
generated declares the contract; custom implements it
generated/ui-extension.tsx defines targeted extension types. Implement cells, columns, actions, controls and wrappers in custom/ui-extension.tsx. custom/extension.tsx contains page hooks and full replacements through PageOverride.
Targeted extensions have specific contracts for editable string/text controls, wrappers and media. Slots do not allow arbitrary replacement of every UI element. An extra column uses the already loaded page of data; it does not automatically add server-side sorting or filtering across the whole list.
Two ways to customize the interface
| Approach | What the generator updates | What you maintain |
|---|---|---|
| Targeted extension | The page, standard controls and new fields you have not overridden | Your component, action or cell renderer |
| Full PageOverride | The generated page remains separate | All content and behavior of the selected page |
Routing uses EntityNameListPageOverride ?? EntityNameListPage: if no custom component is set, the generated page opens. Configure PageOverride in source; there is no Generator UI switch for it.
Practical guides
- Custom logic and interface in custom zones
Extend or replace the home page through
admin/src/app/custom/dashboard.tsx, separately from entity-specific features. For standard-field grouping, start with the visual editor: rows, columns, headings and tabs are stored in the model and applied through Generate.
Declarative presentation and custom ownership
Branding generates shared appearance/configuration and publishes copied branding assets under admin/public/branding/. Source assets stay in .admingen/branding/ with the authored model. Configure standard appearance in Project settings instead of editing generated theme or layout files.
The independent features.customDashboard flag controls whether router composition imports the team-owned home wrapper. Disabling it does not delete the extension. Form layout, Demo configuration and appearance remain separate from API authorization.