[GH-ISSUE #4587] [FR] Block reference inside document workspace #2053

Closed
opened 2026-03-23 21:19:16 +00:00 by mirror · 5 comments
Owner

Originally created by @emmggi on GitHub (Feb 2, 2024).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/4587

Description

We should have referencing blocks from other documents. Reference should either include that block somehow highlighted or elevated to let the user know it's a reference or should have a small link that lets you hover over it or click it to reveal the contents of the referenced block. These two could also be separated into:

  1. Linking a block - that would give a preview on hover or click. This would also be useful for linking to current page blocks.
  2. Embeding a block - this would embed the referenced block.

Referencing/linking a block should be through the / menu and we should have a small popover with a search field to search for the block by its content.

Having that block deleted should leave a placeholder saying it was removed.

Impact

Document workspace users.

Additional Context

Logseq has this feature. It's very helpful when you try to, for example, fill in the details of a subject from another document.

Originally created by @emmggi on GitHub (Feb 2, 2024). Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/4587 ### Description We should have referencing blocks from other documents. Reference should either include that block somehow highlighted or elevated to let the user know it's a reference or should have a small link that lets you hover over it or click it to reveal the contents of the referenced block. These two could also be separated into: 1. Linking a block - that would give a preview on hover or click. This would also be useful for linking to current page blocks. 2. Embeding a block - this would embed the referenced block. Referencing/linking a block should be through the `/` menu and we should have a small popover with a search field to search for the block by its content. Having that block deleted should leave a placeholder saying it was removed. ### Impact Document workspace users. ### Additional Context Logseq has this feature. It's very helpful when you try to, for example, fill in the details of a subject from another document.
Author
Owner

@annieappflowy commented on GitHub (Mar 25, 2024):

I just wanted to ask if there are plans on implementing linking particular blocks? This is a function that I heavily use in LogSeq, but I really enjoy AppFlowy and would like to hop completely into it. I love the flow and UI, database functionality is great (though some additional feature might be in order), it greatly enhances my work. But I'm quite often referring particular blocks within a page, instead of writing "Refer to page X", because those can become quite big.

<!-- gh-comment-id:2017037460 --> @annieappflowy commented on GitHub (Mar 25, 2024): I just wanted to ask if there are plans on implementing linking particular blocks? This is a function that I heavily use in LogSeq, but I really enjoy AppFlowy and would like to hop completely into it. I love the flow and UI, database functionality is great (though some additional feature might be in order), it greatly enhances my work. But I'm quite often referring particular blocks within a page, instead of writing "Refer to page X", because those can become quite big.
Author
Owner

@annieappflowy commented on GitHub (Apr 23, 2024):

Is there a way to link text to a header?
within the same doc i mean
right but it's meant for referencing
so if someone reads it they can jump to the related paragraph/header

<!-- gh-comment-id:2071341968 --> @annieappflowy commented on GitHub (Apr 23, 2024): Is there a way to link text to a header? within the same doc i mean right but it's meant for referencing so if someone reads it they can jump to the related paragraph/header
Author
Owner

@annieappflowy commented on GitHub (May 1, 2024):

It would be very important to be able to treat the texts as blocks.

<!-- gh-comment-id:2088439411 --> @annieappflowy commented on GitHub (May 1, 2024): It would be very important to be able to treat the texts as blocks.
Author
Owner

@emmggi commented on GitHub (Jul 29, 2024):

Hopefully this is intuitive and quick to use. Maybe ~ could activate a small popover where we enter a search query to find our block. Results should show the block content with our query highlighted and the path of the page it's in.

Fuzzy search would also be very much appreciated.

<!-- gh-comment-id:2256502161 --> @emmggi commented on GitHub (Jul 29, 2024): Hopefully this is intuitive and quick to use. Maybe `~` could activate a small popover where we enter a search query to find our block. Results should show the block content with our query highlighted and the path of the page it's in. Fuzzy search would also be very much appreciated.
Author
Owner

@annieappflowy commented on GitHub (Jun 10, 2025):

Image

We supported copy link to block, which fulfills the basic needs of referencing a block in documents.
I'll close this issue for now.
Please create new issues if you have follow-up requests.

<!-- gh-comment-id:2959612156 --> @annieappflowy commented on GitHub (Jun 10, 2025): <img width="383" alt="Image" src="https://github.com/user-attachments/assets/bdc774ee-3f82-4de0-a607-5c69ddaef14f" /> We supported copy link to block, which fulfills the basic needs of referencing a block in documents. I'll close this issue for now. Please create new issues if you have follow-up requests.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
AppFlowy-IO/AppFlowy#2053
No description provided.