# Discussion about a new Dashboard **URL:** \ **Category:** Dashboard\ **Created:** [16 September 2021 18:31 UTC](https://discourse.nodered.org/t/discussion-about-a-new-dashboard/51119 "2021-09-16T18:31:02Z")\ **Posts on this page:** 1\ **Showing post:** 101

**Author:** ![BartButenaers](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bartbutenaers/32/10476_2.png) [@BartButenaers](https://discourse.nodered.org/u/BartButenaers)\ **Post date:** [25 September 2021 05:37 UTC](https://discourse.nodered.org/t/discussion-about-a-new-dashboard/51119/101 "2021-09-25T05:37:09Z")

> [@meeki007](#): > > I had a shift in my thought. The basic Dashboard what ever one we as a community decide to use/support should not have the complexity and maintenance of multi user support Ok not sure whether my usage would be multi-user or not to be honest. We had a very interesting discussion about having 'affordable' [touch screen](https://discourse.nodered.org/t/wall-mounted-node-red-touch-screen-device-request-for-ideas-and-volunteers/51136) devices in the rooms of a house, where a Node-RED dashboard is being displayed. And each room needs to display another Node-RED dashboard: e.g. in the entrance hall you want to display a dashboard with an alarm keypad, in the bathroom you want to show temperature/humidity, and so on... To summarize: wall mount Amazon Fire 7 tablets which display a dashboard running on a central Raspberry, because such devices have not enough system resources to run Node-RED locally. _But it would be very pity if I had to install N Node-RED instances, to host N different dashboards._ Such typical home automation situations should be easy to implement using a single Node-RED instance IMHO ... But perhaps you guys have already other solutions in mind for this. > [@tve](#): > > which has a different set of benefits, such as being able to deal with the layout stuff easily and being able to create arrays of widgets programmatically. Yes indeed that is something that is not easy to solve in the current model. Entirely correct. Going to ask some (perhaps stupid) questions to understand it a bit better: - When you say "_ **programmatically** _" then you mean a code snippet in the layout manager, or something else? I have not needed something like that yet, but I can imagine that some folks program this kind of stuff in a UI template node currently? Or do you mean that it is currently (in a template node) only possible for basic widgets (e.g. md-button) and that you can e.g. not add N instances of my node-red-contrib-ui-svg node on a screen programmatically, to show the floorplans of N floors in my house? - When you say "_ **layout stuff** _" do you mean an easy way to specify css styles, or an out-of-the-box available layout manager? Because I can indeed understand that you want to use an existing layout manager, to avoid reinventing hot water. It is not a secret anymore that I like the current model, so I am going to give it yet another try 🙄. @Steve-Mcl integrated some time ago a third party SVG editor inside our node-red-contrib-ui-svg node, because we didn't want to spend the remaining of our miserable lives to develop a graphical SVG drawing editor ourselves. So we _ **integrated** _ an existing SVG editor (DrawSvg) in our node. Isn't something like that possible perhaps. That you can access the third-party layout manager easily from the flow editor, and the layout manager shows and manages the UI nodes in Node-RED. I mean _ **dual way** _ (like we do with DrawSvg): This was most probably my last attempt to keep having my belovely UI node concept in Node-RED. It is something I really like... Absolutely not because "_I got used to it_", but because it was one of my main reasons why I choose Node-RED at the time being. And I still like the concept, to have all my stuff in the same Node-RED way... But if the developers of the new dashboard have another opinion about that, then I will rest my case from here on ... --- _[View the full topic](https://discourse.nodered.org/t/discussion-about-a-new-dashboard/51119)._