Build
This section covers the practical work of building Mateu UIs. Each page goes deeper into a specific aspect of the framework. The pages follow a progression from the outer shell inward, and from simple to advanced.
Start with the shell and navigation — these define the frame every user sees. Then move into domain modeling and CRUD, which is where most of your application code lives. Finally, tackle advanced composition patterns like master-detail, custom row actions, and full orchestrator control.
If you are building something new, read the pages in order. If you are solving a specific problem, jump directly to the relevant page.
Pages in this section
Section titled “Pages in this section”Shell and navigation
Section titled “Shell and navigation”- Application shell — the outer frame: title, logo, sidebar, layout variants
- Dashboard home page — KPI cards, charts, and activity feeds on the landing page
- Navigation and menus — how menus, routes, and sub-menus are declared
Domain and data
Section titled “Domain and data”- Domain models — how ViewModels relate to your backend architecture
- Foreign keys and options —
@Lookup, options suppliers, and label resolution
- CRUD navigation flow — the list → view → edit flow and how to customize it
- Customizing CRUD and listings — visibility, layout, actions, and adapter customization
- Listing row actions — per-row actions using
ColumnActionandColumnActionGroup - Full control with CrudOrchestrator — explicit models for filters, rows, views, editors, and creation forms
Composition
Section titled “Composition”- Relationships vs embedded CRUDs — when to use
@Lookup,List<Entity>, or an embedded orchestrator - Master-detail — embedding a child CRUD inside a parent screen
- Golden example: Orders, Customers and Order lines — a complete business UI combining all of the above