Get started / NEXT HMI documentation
NEXT HMI documentation
A task-oriented guide to building operator dashboards: projects, the editor, widgets, layout, OPC-UA data, dynamic properties, theming, alarms, recipes, and custom widgets.
Get started
| Page | What it covers |
|---|---|
| Overview | The mental model — runtime and editor together, a project is a folder, every property can bind, one socket for data |
| Getting started | Choosing how to run it, and the first run step by step |
| Installing and running | Docker and portable-binary installation, HTTPS, the on-disk model |
| Managing projects | What's in a project folder, the Manager dashboard, downloading, uploading, adding and removing projects |
| Files & assets | Images, icons, third-party libraries — where they live and how to add them |
| Licence | AGPL-3.0 in plain terms, your project content, and when you'd want a commercial licence |
The editor
| Page | What it covers |
|---|---|
| The editor workspace | The config areas and the working habits worth knowing |
| Pages & navigation | Adding pages, grouping and nesting, giving operators a way around |
| Adding & arranging widgets | Placing widgets, schema-driven properties, making controls do something |
| Layout & responsive design | Containers, shell regions, free placement, one project on every screen size |
Data
| Page | What it covers |
|---|---|
| Connecting to data | The OPC-UA wizard, and designing offline with a static datasource |
| Binding & subscribing | How a bound value reaches the screen, and what a subscription costs |
| Dynamic properties | Type vs. source, the value types, every source, and how they nest |
Widgets & styling
| Page | What it covers |
|---|---|
| Built-in widget catalog | Every shipped widget and its properties — generated from the registry |
| Theming | Design tokens, and theming your own widgets |
| Alarms & recipes | Condition-based alarms, and parameter sets you load to live variables |
| Building your own widgets | The custom-widget SDK, the build pipeline, and authoring rules |
Automation
| Page | What it covers |
|---|---|
| AI agents over MCP | Letting an assistant read and edit a project — enabling it, tokens, and the limits |
Working on NEXT HMI itself rather than building with it? The architecture and API reference is in docs/dev.