Frontend addresses flows and dashboards by id: routes /flows/$flowId, /dashboards/$id and /view/$id, query keys, saves, lists, device pickers, search, brain and endpoint links and generated results dashboards go by id, while live values, issues, pauses and message names keep the key; tabs take the title from the document; creating uses POST and opens the issued id; the flow and dashboard panels show key and id with a copy button and a served HTTP or WebSocket node shows its hook URL under the flow id; specs create by POST and ids.spec.ts exercises issued ids

docs/interface/dashboards.md

@@ -256,6 +256,12 @@ when no usable message value is available.
 
 To change one on a schedule, have a scheduled node publish its bound message.
 
+The top of the panel shows the dashboard's key and its id, with a copy button
+for the id. The id never changes: the editor, `/view/{id}` and the devices
+showing the dashboard all use it. A dashboard from before ids were introduced
+kept its key as its id, while one created now gets an opaque id such as
+`d_k3q7m2xa`. The tab shows the title.
+
 ### Look and theme
 
 **Fluksio** is the default look. **Material** uses flat tonal cards; **Glass**
@@ -448,7 +454,7 @@ under the finger, as a tile view moves.
 
 ## Showing one
 
-Open `/view/{name}` for a dashboard-only view with your normal session.
+Open `/view/{id}` for a dashboard-only view with your normal session.
 For a dedicated screen, pair a device.
 
 ## Devices: hanging a screen on a wall