Request for feedback: Flow Library Categories

General
1

With over 5000 nodes listed in the library, a common piece of feedback we get is the challenge of finding the right node for a given task.

One of the steps we're taking to tackle this is to introduce the ability to browse the library by category.

We've done the work to enable this in the library code base, but it hasn't been turned on for all users yet because we have the small task of deciding what categories to have and then classifying the existing nodes in the library.

I've come up with this initial set of categories to use and would like feedback on it.

Some considerations:

  • It needs to be a manageable list of high-level categories
  • We can add/remove categories in the future - this is a first iteration
  • Nodes can be in multiple categories where this is overlap
  • Initially, the choice of category will be curated by admins/moderators on the site
  • The category info will get included in the catalog json used by the editor - and we'll update the palette manager UI to also support search-by-category

Here is the initial list.

  • AI
  • Analytics
  • Communication
  • Dashboard
  • Database
  • Hardware
  • Industrial
  • Plugin
  • Storage
  • Tools
  • Utility

Are there any other top-level categories you think should be included?

1 Like
2

Plugin may be redundant/confusing because aren't they all 'plugins' ?
An additional category I could think of; 'logic' and maybe 'parsers'

sidenote for the filters; personally I would go for a single selection instead of multiple, with nodes as default.

3

Maybe a Home automation category.

3 Likes
4

Whilst technically no... that isn't a distinction users should have to care about. I've renamed that one 'Tools' as I think it covers the same ground - things that enhance the editor experience, rather than nodes for the flow.

5

Hi, to establish categories is a good idea :wink:
Perhaps a "Security" category can make sense

1 Like
6

I think "UI" instead of Dashboard too as its a more general purpose category, and one that newer users would recognise

2 Likes
7

I am wondering whether Industrial should instead be called something like Measurement and Control, so that it covers home automation.

8

Charts as a separate category? Dashboard would be a larger bucket.

9

Agree (unsurprisingly) that UI is better than Dashboard (having both would be confusing).

Maybe consider "Transformation" or "Data Transformation"? for nodes that manipulate data but don't fall into other, more explicit categories.

Oh, and of course you need "Security" :wink:

10

Operating System Integration?

Eg the built in exec. Node-red-pythonshell etc

11

Oh, yeah, good call. Could feasibility come under tools but I definitely agree with this one (or something similar). Good shout IMO

12

I always think the editor is also a UI, as that's where users design their flows. Therefore 'dashboard' 'Dashboard' imo is more specific, and should be used.

2 Likes
13

Very confusing though if you aren't looking for a Dashboard (capital D) node.

Maybe you WANT a plugin that will affect the Editor UI? Or a UIBUILDER node. Or some other UI creating/amending node? None of those would be obviously looked for under "Dashboard" would they?

1 Like
14

Dashboard, just as it's written in the first post in this topic.

I don't think users think that deep!
Speaking as an average user, if I wanted a node for my Dashboard, I would expect to look in the Dashboard category :smiley:
Maybe you top tier techies view things differently?

15

It isn't a problem having a category called "Dashboard" for Dashboard nodes. What I'm saying is - what about all the other types of UI related node? Why would anyone look for a plugin that impacts the Editor UI look in a category called Dashboard? They wouldn't would they? So at least, you'd still need another category, not just Dashboard.

1 Like
16

Will there just be a single top level, or eventually sub-levels beneath them, to allow users to drill down into the category?
Example, @smanjunath211 mentioned above 'Charts' which instead of being top level, sat underneath 'Dashboard'.

Maybe with over 5,000 contrib nodes, a second level may be justified?

17

Is User Interface better than Dashboard?

1 Like
18

We obviously don't agree, and we could probably keep this going all night :woozy_face:
We've both made our points, let's not further pollute this topic.

2 Likes
19

I would add Home Automation as E1cid mentioned above because there are a lot of nodes. e.g. Alexa, HomeKit, Home Assistant, ...

4 Likes
20

But thats because you've used Node-RED for years, and so are used to calling it a "Dashboard", I would expect new users to think "UI" for nodes that give them buttons, charts, etc

1 Like