Dashboard is Sero's home surface for compact app and workspace summaries. Widgets are small panels contributed by the host or by installed apps/plugins; they are useful for status at a glance, not a replacement for opening the full app.
Dashboard layout is saved in profile layout state, so it follows the active profile.
If the Dashboard is empty or the widget list is short:
Do not assume every app has a widget.
| Type | Plain-language meaning | Notes |
|---|---|---|
| Manifest widget | Declared by an app/plugin package manifest | Available when the host discovers the app manifest. |
| Runtime widget | Registered by app code during a renderer session | Can appear/disappear with the app/runtime lifecycle. |
Both types mount inside Sero's app runtime provider so they can read app/workspace context where supported.
Dashboard uses a draggable/resizable grid. Widget sizes and positions are user-adjustable hints, not fixed guarantees across every screen size or future alpha build.
Typical actions:
Dashboard layout is stored with profile layout state:
That state can include widget instances and grid layout details. It is local profile data and can reveal installed apps, workspace habits, and private project names through widget titles or state. Redact before sharing.
Sero does not use browser localStorage as the public persistence model for dashboard layout.
Widgets are best for:
Open the full app when you need rich editing, long lists, detailed settings, or sensitive data review.
| Symptom | What to try |
|---|---|
| Widget not listed | Confirm the plugin/app is installed, enabled, compatible, and actually exposes a widget. |
| Widget disappeared | Runtime widgets may depend on app/runtime lifecycle; reopen the app or restart Sero. |
| Layout looks wrong | Resize the window, drag/resize widgets again, or restart from the same profile. |
| Widget shows stale data | Open the owning app or refresh the relevant plugin/runtime state. |