Extending The Dashboard
Overview
How a custom Nuxt layer plugs into the DMS dashboard — the registration model and the catalog of extension points.
The DMS frontend renders backend-described pages out of the box. When you need to go beyond what the built-in components cover, a custom Nuxt layer (Frontend layer) registers extra capabilities into the dashboard. This section is the catalog of those registration points — the table below lists them; the next section, Frontend composables, covers the composables your layer's Vue consumes.
What you can extend
| Extension | Adds | Chapter |
|---|---|---|
| Dashboard chrome | Header buttons, command-palette groups, sidebar widgets, app widgets and overlays, footer links, auth-page links | Dashboard chrome |
| Theming & branding | Your logo, palette, fonts, and design-token overrides | Theming & branding |
| Custom data types | A new field/column type (the Vue behind a backend @RegisterDataType) | Custom data types |
| TableView displays | An alternate table body renderer (kanban, cards, calendar…) | TableView displays |
| Component events | Cross-component reactivity — one component reacts to another's events | Component events |
| Period filtering | Link widgets to a shared date-range via a scope id | Period filtering |
File storage
Wire a storage backend for the file and image types, configure FileType constraints, and understand the staged-upload lifecycle.
Dashboard chrome
The registries a frontend layer calls to add header buttons, command-palette groups, app widgets, sidebar widgets, global overlays, footer links, and auth-page links to the dashboard shell.