Features
Triage

Missing function for linking Pages: restricting the scope to certain Collections

What's the scenario?

When I select a word in a text Block, and want to link it to another Page, a menu appears in which I can choose an existing Page -- good✔

It's also possible, to search in that list, by starting typing -- good ✔

What I miss:
Limiting the scope of that search to a certain Collection.

What's the goal?

Imagine, you're in the Wiki. And you want to link to another Page in that Wiki.
You are not interested in seeing thousands of Pages in the choose list that are somewhere else in the Space and that live in other Collections.

It may even be what you not clearly remember the target's name, therefore it could be that the existing search function overwhelms you with way too much suggestions when you start typing.

But it's often highly likely that you at least remember in which Collection the wanted target Page lives.
Therefore it would be nice to be able to limit the scope of the search in that choosing list to a certain Collection.

In the mentioned case that you are in the Wiki, it could be a good idea that the search scope is already pre-restricted to the Wiki. so that Pages from other places don't appear in the search -- until you remove the restriction.

My video shows only what I talk about.
Actually, there are no "thousands" of Pages in that Space, therefore it looks as if the search would easily work when I start typing.
But with lots more Pages, it can become tedious to find the right target, especially if you can't remember its exact name.

1 Comment

Sign in to comment

AL
Alex Lins (Bao)·about 3 hours ago

Thanks for the detailed walkthrough — the video makes the use case clear. To help us scope this right:

  1. When you're in a Collection (like your Wiki) and link a word, should the search default to that Collection only, or just have a filter toggle you can flip on/off?
  2. If you're linking from a Page that's in a sub-Collection, should it search just that Collection, or that Collection + its parents/children too?
  3. Are there cases where you'd want to link across Collections often enough that a default scope would get in the way?