docbox docbox
  • About Mateu
  • Java
  • Kotlin
  • C#
  • Python
  • Design systems
  • Native
  • AI
GitHub repo
to navigate to select ESC to close

  • Create your project

    • Prerequisites
    • Springboot MVC
    • Springboot Webflux
    • Micronaut
    • Quarkus
    • Helidon MP

  • Java

      • Quickstart
      • First app
      • Admin panel
      • Distributed backoffice
      • Embedded UI
      • State, actions and fields
      • Validation
      • Field stereotypes
      • Declarative vs fluent
        • Using state in fluent components
      • Action behavior
        • Returning multiple results
      • Model vs Pages
      • Routing and parameters
      • UI vs Route
      • ViewModel lifecycle
      • Execution model
      • Application shell
      • Navigation and menus
      • Foreign keys and options
      • Domain models
      • CRUD navigation flow
      • Relationships vs embedded CRUDs
      • Master-detail (Process + Steps)
      • Golden example: Orders, Customers and Order lines
      • Customizing CRUD and listings
      • Full control with CrudOrchestrator
      • Listing row actions
      • Rules
      • Breadcrumbs
      • Layout and composition
      • Custom web components
      • Extensibility
      • Testing
      • Security
      • Case study: Distributed control plane (SSR → SSG)
      • Case study: SSR to SSG control plane
      • Mateu in hexagonal architecture
      • Service-owned UI modules
      • Query services and UI rows
      • Lookups backed by query services
      • Workflow and forms integration

  • Components

    • Overview
    • Fluent components
    • Layouts
    • Forms
    • Supported components
    • Grids
    • Actions
    • The component tree
    • Client-side logic
  • Java
  • Java
  • Start here

Start here

This is the shortest path to becoming productive with Mateu.

Recommended order

  1. Quickstart
  2. First app
  3. Admin panel

For most developers, the quickstart is the best first stop.