as you probably know there are plans to unity Classic UI, Modern UI and the control part of Paper UI into a single application. Unfortunately the current sitemap mechanism is textual configurable only and the REST interface (that is used by UIs) is not prepared to support modifications. To be more user-friendly for newcomers the idea is that the future UI can however let the user manipulate the sitemap by a sitemap-builder or by live-reordering of sitemap elements etc.
For compatibility and migration reasons, the old sitemap and the new sitemap interface need to coexist for a time. This thread is about to find a name for sitemaps2, that can be used on the REST interface and in the user interface to distinguish it from āsitemaps1ā.
This thread is NOT about to discuss if that makes sense. Please open a second thread if you feel the need to discuss that.
The name is preoccupied at the moment with the very first page you see. But that page will be incorporated in the future UI, so the name will be free again. So dashboard is in the race.
There are already nice suggestions. Iāll start a poll end of the weekend.
Please consider that the REST api endpoints are all-lowercase. Dashes are fine. Ideally the name openHAB (or parts of it) does not appear in your suggestion.
Interesting restrictionā¦then I would suggest just āhomeā as name. It is very intuitive for what a sitemap really representsā¦in my mind at least.
Alternatives are āhome-uiā (but then the UI appendix makes it less accessible).
Yes, Iām curious about that too. In an āEclipse Smarthomeā world, it would make sense to avoid openhab-y branding, not clear what the driver is now.