Improve the experience of linking to a Page

[0xDing]

Problem

Articulate the problem that this piece of work addresses

We need a flexible way to display links to its sub-pages in the content of a page and allow users add link to other pages simply.

What is the status quo and why does that not work?

We currently have the SubPage Menu Block, but it is too coarse-grained. And Embed block, which currently does not have good support for Link to Page.

Why does the problem matter?

For workspaces with a large number of pages, this will significantly improve the navigation experience.

Why is this the right time to address this problem?

We should prioritize this problem to improve the basic usage experience.

Time Budget

3 days

Solution

• Remove SubPage Menu block
• Making a Page Block visible in content means that all sub-pages are displayed as PageBlocks in content. When a PageBlock is deleted, the corresponding Page will also be deleted.(see #Out of Bounds)
• Add a /page command to the slash menu to support linking to a page or creating a sub-page and linking to it.
  

Out of Bounds

In the future, we will solve the problem of the inability to organize pages visually in a tree-like structure with the "Smart Page List" epic. So, this epic focuses only on how to display page links in the Page Content better.

Rabbitholes

/page is a slash command rather than a block. It provides a popover to create an embed block(in text view) for an existing page or to create a new subpage. We may also need to improve the experience when linking embed blocks to pages.

• Are only text views supported for embed blocks linked to a page?
• Support searching and selecting pages in the URL field of the embed block's popover.

[stackia]

owner @melchior-voidwolf

[BrickDoctor]

We don't have a page block now, but the link block still retains the underline style

[melchior-voidwolf]

One result of the current discussion.
We need to add a pagelink component
This component should be an in-line component like formula

It can be inserted quickly by calling up the slashmenu with '/', or it can be inserted via explorer

When a newpagelink is inserted, the component should be activated and a modal should pop up to select the linked document

(An extensibility point: essentially, the anchor is an optional attribute of the link, and while it may be difficult to support at this stage, it should ideally be considered.

Extending from this fact then, thepagelink may come with additional properties to locate specific anchor points or blocks!!! )

When a pagelink is activated, there will be a list of equal choices that can be searched to locate relevant content
The priority of the relevant content is defined as:

• Subpages
• Recently used pages
• All pages
• This page itself (considering the anchor claims, links to the page itself should be supported)

[0xDing]

It might be better to have the embed block support the link page

[0xDing]

anchor is an optional feature

[melchior-voidwolf]

At the bottom of the page you can append a "Add Subpage named "${searchText}""
Click on it to add a subpage and link to it

[melchior-voidwolf]

@0xDing

[melchior-voidwolf]

To avoid the formation of a mesh, it is forbidden to connect to yourself

[zaotang]

The above figure is the process design of this function,t here is a problem that needs to be confirmed by @melchior-voidwolf :
How to recommend and sort pages in the modal popover？

Here is the UI design:
https://www.figma.com/file/pKCVegQsV7NqwMfhapeWmR/Web-UI---G-Embed-1.0?node-id=8131%3A151223