Display something other than "Nothing to See Yet" when inside a top-level folder (with sub-collections inside it).

[pawlodkowski]

Is your feature request related to a problem? Please describe.
When clicking on a "top-level" collection (i.e. a collection which itself does not directly have dashboards inside of it, but has sub-collections inside of it, which in turn contain dashboards), there is a message "Nothing to see yet." that takes up more than three-quarters of the screen (see screenshot below).

Now, of course, the user can figure out that there are more folders to click through until they finally get to the content, but I find it a bit strange that this giant screen is shown instead of something a bit more useful, or at least something other than "nothing to see yet", which is actually misleading.

Describe the solution you'd like
Ideally, there would be a screen that displays some sort of visual indication of the content hierarchy (e.g. kind of like what is in the left pane), or perhaps at least some other message saying something like "See the sidebar for sub-collections, which contains all the information".

Describe alternatives you've considered
As @flamber has already suggested in the original Discourse post about this issue, the workaround would be to add a "placeholder" question or dashboard, which can be named "See the sidebar for sub-collections, which contains all the information". This would work in the sense that the screen would not being showing the "Nothing to See Yet" message, but it is a manual workaround that isn't very elegant.

How important is this feature to you?
My stakeholders in general love the Metabase tool that my team maintains for them (much more so than the previous BI tool that is being replaced), but the only point of criticism was the navigation / folder structure, which most of them found a bit unclear at times (e.g. this current issue). In my opinion, Metabase is one of the best in terms of UI / UX / aesthetics (e.g. drill-throughs, on-click actions menu, minimalistic design), so this strikes me as a low-hanging-fruit / must-have in terms of clear, unambiguous UI and navigability that is consistent with Metabase's reputation.

⬇️ Please click the 👍 reaction instead of leaving a +1 or update? comment

[pawlodkowski]

@flamber FYI it looks like this issue has been solved recently! I'm not exactly sure when, but I thought it'd be worth marking this issue as solved for future reference / transparency.

The following screenshot is from version v0.46.6.2: