# FlexDash: towards a new dashboard for Node-Red

**URL:** <https://discourse.nodered.org/t/flexdash-towards-a-new-dashboard-for-node-red/45879>\
**Category:** Share Your Projects\
**Created:** [18 May 2021 20:04 UTC](https://discourse.nodered.org/t/flexdash-towards-a-new-dashboard-for-node-red/45879 "2021-05-18T20:04:29Z")\
**Posts on this page:** 1\
**Showing post:** 67

<div class="post-metadata">

**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:** [27 June 2021 22:00 UTC](https://discourse.nodered.org/t/flexdash-towards-a-new-dashboard-for-node-red/45879/67 "2021-06-27T22:00:06Z")

</div>

> [@tve](#):
>
> Is there another option?

Some time ago I had created a node that offered some configuration, but my node didn't really worked with input/output messages. The [feedback](https://discourse.nodered.org/t/announce-node-red-contrib-xterm-second-beta-sidebar/19718) I got from the community was that I had to create a (right) sidebar panel in the flow editor, instead of putting my configuration on the config screen of a normal node. And they were right, so I created a _**(right) sidebar panel in the flow editor**_. Because I realized at that moment that I had developed a node, only to have a config screen where users could enter the configuration data. But indeed it wasn't really a full blown node, that handled messages...

Could that perhaps be a better solution for your use case, if you don't have an input or output? Regardless of the extra work involved of course...

---

_[View the full topic](https://discourse.nodered.org/t/flexdash-towards-a-new-dashboard-for-node-red/45879)._