Improvements
Done
Navigation : Selecting Another Page Without Returning to the Collection View
I open collection pages in full-screen mode.
I often need to switch pages, and currently this requires me to return to the collection view, search for my page, and then finally click to open it.
For example: it would be very convenient to be able to do this from the breadcrumb trail. Hovering the cursor over the page name would display a list of other pages.
5 Comments
Sign in to comment
Is there any reason why you don't use the side peek feature, which is explicitly designed for this flow?
Side peek can be useful for quick edit.
Not for more demanding tasks (creating multi-column layouts, large tables, etc.), unless maybe you have a very large screen?
I create detailed notes (on apps, for example), and I don’t want to have to write them on a Post-it note in the corner of my screen (yes, pehaps I’m exaggerating a bit, but it really captures how I feel).
That’s also the whole point of offering the choice between full-page view and Side Peek. In fact, I use Side Peek more for quick reference than for editing (from my perspective and based on how I use it, it was really designed for that purpose).
Yes, I imagine this has more to do with screen size than anything else—which is fair enough since a macbook air vs. a 32-inch monitor is very different (I'm on the latter).
How do you feel about just using CMD+K search in a well-designed pop-up window and finding the object you want that way?
You can imagine my hesitance of implementing too many unique UI behaviours that only show up in certain mini apps/scenarios vs. having a universal solution that can solve many situations.
You’re offering two types of views (which apply whether you want to read or edit items). I suppose we agree that they both have their merits (even if we disagree on their intended use) and their target audiences.
Isn’t it a shame if one of them is less “functional” than the other? It’s a bit like the Anytype debate about the stripped-down sidebar versions that resulted in lost functionality.
Yes, I admit I can do without it (navigating from page to page is more important to me, for example).
No, I wouldn’t use CMD+K: replacing a two-click navigation with a keyboard shortcut, entering filters to display the target, then selecting it—I’d rather go back to the collection.
Notion added this feature a while back. I didn’t notice it right away—it was the overwhelmingly positive feedback from other users that made me discover it. And I loved it, too! In fact, it’s even more powerful than this request.
Here’s a current use case to wrap up my argument: I’m doing some home improvement projects. When I’m working on plans, purchases, or other tasks, I navigate a lot between different records, all stored in a single database/collection.
I don’t edit them, so a “last page” widget wouldn’t work. No bookmarks either—I’d need dozens per project (sometimes the entire collection).
With this two-click solution, I can switch from one to the other.
In short, I’m making my case, but this is by no means a priority—it’s just a nice little feature. I’m fine with leaving the proposal open to user votes; I won’t complain 😁.
There's no doubt that when you look at any feature in isolation, that it has a lot of merit. And I do see the value here. Let's see how it goes. I can imagine that there will be navigational conflicts as users navigate across different collections/miniapps and I hope we can get the behaviour of this thing to work as intended.