Request for feedback: Flow Library Categories

It'll be single level for now, and ideally minimal categories as to not get too complicated

1 Like

When I suggested User Interface might be better than Dashboard I also wanted to hint that UI is less intuitive since it can be misinterpreted as University of Iowa.
Or (apparently) Urinary Incontinence. :slightly_smiling_face:

1 Like

...but the latest 'UI' environment that accommodates buttons, charts, etc has been called 'Dashboard 2'??
Regardless what the category is called, I'm sure I'll find what I need anyway :smiley:

Or maybe split the difference ? - User Dashboard

1 Like

My Two cents, I vote UI

"Presentation"?

Not all UI's are Dashboards or even dashboards. :smile:

Thanks for the comments and suggestions. Will take them all on board as we move forward.

We have now made the initial list of categories live on the Flow Library.

The list is based on the feedback in this thread, along with some further changes once I spent some time classifying nodes and saw where we needed other things (for example, I added a date-and-time category as there are lots of nodes in that area).

I appreciate all the input - I acknowledge that not everyone's suggestions have been included, but I hope this list provides a useful starting point.

In practical terms, I have manually classified the 700 most downloaded nodes (according to last week's snapshot). I will continue to chip away at the list, but I do not plan to proactively classify nodes that are receiving very few downloads.

Right now, @dceejay and I are able to classify nodes (not that I've told Dave yet...). I plan to open this up to a larger group of trusted moderators on the site. We will also look at how to enable node authors to self-classify nodes as they are added.

3 Likes

Is there something against adding a "categories" entry in the "node-red" section of the package.json? Any category that is used and isn't in the list would simply be ignored.

Something like this:

"node-red": {
    "version": ">=2.0.0",
    "plugins": {
       ...
    },
    "nodes": {
     ...
    },
    "categories": ["cat1","cat2",...]
   ...

it wouldn't need to be mandatory but could save the maintainers much time.

That is certainly an option. There is also the standard keywords section in the package.json file - something we already capture. So rather than add something custom, we could look for known category names in that.

But then it does get a bit fiddly where we want to be able to classify nodes independently of what they claim (or don't) in their package.json; handling updates becomes a bit trickier to keep things in sync.

The main reason I didn't start with this approach was not wanting to require node authors to republish their packages to get the categories bootstrapped with content.

3 Likes

Nice! Makes life easier for sure.

Not sure if it is intentional, but search and category dont seem to work together. For example, I search mssql and get 2 pages. So i narrow it down by clicking database category - now there are 3 pages and the search term is no longer applied.

while I am here writing words:
Also, If I sort by downloads, then when I enter a different search term, Sort by is its revered "Recently Updated". could we persist this for the session?

But that's an npm thing right? That's where I put in "node-red" as indication that the package is intended to be used with Node-RED.

I can definitely understand that but as an active publisher, I can easily add a list with the next release.

Don't you risk having package authors wanting to be categorised differently? It's kinda weird to be able to publish to the catalogue but not being able to define the category for the package - as author.

It's kinda six of one and half-a-dozen of another ...

Can this blue also be changed to some coffe-like color

Would propse something like this:

.filter-options input {
    cursor: pointer;
    accent-color: #aa6767;
}

May happen that Safari doesn't eat it but all others should do ...

Are you hitting 'Enter' after typing a search term? If so, that's a known issue reported earlier in this thread. Will get to it.

Yeah Nick, I am :face_with_open_eyes_and_hand_over_mouth:

thanks for the reminder to wait 300ms :slight_smile:

1 Like

Yeah, looks like there's a disconnect somewhere. WIll sort that out.

1 Like

@Steve-Mcl searching by term with categories selected now fixed.

That's all you're getting from me today - but please do keep the feedback coming.

Thanks a bunch Nick. Have a good weekend.