Use cases
Each use case is a complete, working example that shows one real-world pattern from start to finish.
Read them in order to build up from basic CRUD to distributed and embedded scenarios, or jump to the one closest to your situation.
CRUD and listings
Section titled “CRUD and listings”- Admin panel — full CRUD from a Java model; status badges, nested collections, column actions, toolbar buttons
- Users CRUD with lookups — Spring injection,
@Lookupfields, checkbox stereotype, custom editor page - Custom listing —
Listing<Filters, Row>, toolbar actions, JWT extraction, auto-load trigger - Nested CRUD — hierarchical data,
@DetailFormCustomisation, modal editors
Architecture and integration
Section titled “Architecture and integration”- Distributed backoffice — one UI composed from multiple microservices, each owning its own UI module
- Embedded UI — drop Mateu into React, Vue, or plain HTML without replacing your existing frontend
Choosing a starting point
Section titled “Choosing a starting point”| You want to… | Start with |
|---|---|
| Build a basic CRUD from a Java model | Admin panel |
| Add a lookup field or custom editor | Users CRUD |
| Query a custom data source | Custom listing |
| Manage hierarchical / parent-child data | Nested CRUD |
| Compose UI from multiple services | Distributed backoffice |
| Add Mateu to an existing frontend | Embedded UI |