mirror of
https://github.com/AppFlowy-IO/AppFlowy.git
synced 2026-03-24 04:46:56 +00:00
[GH-ISSUE #4587] [FR] Block reference inside document workspace #2053
Labels
No labels
2024
2025
2026
acct mgmt
AI
automation
bug
calendar
ci
CJK
cloud
code-block
collaboration
copy-paste
database
data migration
data sync
deploy
desktop
develop
develop
documentation
duplicate
editor
editor-plugin
emoji
export
files
flutter-only
follow-up
formula
good first issue for devs
good first issue for experienced devs
grid
hacktoberfest
HACKTOBERFEST-ACCEPTED
help wanted
i18n
icons
images
importer
improvements
infra
install
integrations
IR
kanban board
login
look and joy
mentorship
mobile
mobile
needs design
new feature
new feature
non-coding
notes
notifications
onboarding
organization
P0+
permission
platform-linux
platform-mac
platform-windows
plugins
program
pull-request
Q1 25
Q1 26
Q2 24
Q2 25
Q3 24
Q3 25
Q4 24
Q4 25
react
regression
rust
rust
Rust-only
Rust-only
Rust-starter
Rust-starter
self-hosted
shortcuts
side panel
slash-menu
sync v2
table
tablet
task
tauri
templates
tests
themes
translation
v0.5.6
v0.5.8
v0.5.9
v0.6.0
v0.6.1
v0.6.4
v0.6.7
v0.6.8
v0.7.1
v0.7.4
v0.7.4
v0.7.5
v0.7.6
v0.7.7
v0.7.8
v0.8.0
v0.8.4
v0.8.5
v0.8.9
web
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
AppFlowy-IO/AppFlowy#2053
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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:
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.
@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.
@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
@annieappflowy commented on GitHub (May 1, 2024):
It would be very important to be able to treat the texts as blocks.
@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.
@annieappflowy commented on GitHub (Jun 10, 2025):
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.