Linking to blocks / Autogenerating IDs for blocks #17264
Labels
domain:ui/ux
This issue reports a problem related to UI or UX.
package:bookmark
package:engine
package:link
squad:core
Issue to be handled by the Core team.
type:feature
This issue reports a feature request (an idea for a new functionality or a missing option).
📝 Provide a description of the new feature
Context
This feature idea came from the work on the Bookmarks (#1944). When we were working on it, we tried to understand how bookmarks should behave on block elements. Should they be added "inside" the block (think
a
insidefigure
element) or before? How user interaction should look? What integrators that create their own block widgets would need to think about?In the end, we decided that bookmarks will be added before those elements. This saved us some amount of time, making the feature more consistent and simpler.
But having linkable blocks is an interesting idea, so we want to gather feedback.
A linkable block is basically an element that a user can link to:
For the simplicity's sake, let's only think for now about the scenario when a block is in the same document as the link to it.
Flow 1:
Or
Flow 2:
The first flow sounds more reasonable, in the second one how would we determine the name of table, paragraph, image on the list? Filename, caption, preview of content? Tricky.
Of course, this could go further into linking blocks across editors. Notion style UI comes to mind with
Copy link to block
:Scope
To fulfill linking to blocks, we would need to:
#
mark before the heading. A user clicks on it, navigates, the URL in the browser changes and it can be copied. But this is a pattern for the published content. To be refined in the future.Materials
If you'd like to see this feature implemented, add a 👍 reaction to this post.
The text was updated successfully, but these errors were encountered: