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

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

• Domain models — how ViewModels relate to your backend architecture
• Identifiable, Named, and SearchableText — the marker interfaces entities must implement to work with the CRUD machinery
• Foreign keys and options — @Lookup, options suppliers, and label resolution

CRUD

• CRUD navigation flow — the list → view → edit flow and how to customize it
• Listings and capabilities — the central model: a Listing<Row> plus the capability interfaces you declare (Searchable, Filterable, Navigable, Editable, Creatable, Deletable); a CRUD is the full pack
• AutoCrud<T> — the simplest way to get a CRUD or read-only listing, with capability annotations
• Customising AutoCrud behaviour — override fetchRows, buildNamedView, or buildCreationForm for custom search, pre-populated forms, and more
• CrudStore — the repository contract consumed by the auto adapters, with Spring Data JPA integration
• Customizing CRUD and listings — visibility, layout, actions, and capability annotations
• Filtered orchestrators — add a dedicated filter model without leaving the auto variants
• Full control with Crud — explicit models for filters, rows, views, editors, and creation forms
• EditableView — single-entity view with an Edit button, no list
• MultiView — the root base class that handles routing and screen wrapping for all orchestrators
• Listing<Row> — standalone listings: toolbar actions, export, and selector support

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