It's quite confusing, UX-wise, that using the search input cannot return flags, operators, or transit results, until you change that scope.
As a user, I expect to find any result just typing the name, and not clicking firstly which tree I want to use, as I could not know where the result lies.
Front-end wise, there are not enough elements in the secondary trees, to avoid merge them all in the homepage. Something like this:
By the way, notice the misplacement of the filters bar after typing something
Yeah - I created the nsi.guide site mostly just to be able to browse the data, not necessarily as a user-focused site. But we can think about changing it to be more user-focused at some point.
It's quite confusing, UX-wise, that using the search input cannot return flags, operators, or transit results, until you change that scope.
As a user, I expect to find any result just typing the name, and not clicking firstly which tree I want to use, as I could not know where the result lies.
Front-end wise, there are not enough elements in the secondary trees, to avoid merge them all in the homepage. Something like this:
By the way, notice the misplacement of the filters bar after typing something