Use case or problem
Apologies for addressing three issues with unlinked mentions in one feature request. Hopefully, you will see that they are all closely related.
- It is difficult and time-consuming to manage a high volume of unlinked mentions, as might occur when linking story bible elements: characters, settings, objects, themes, etc to the related draft/manuscript pages.
- It is not possible (I believe) to limit the scope of backlinks, so that unlinked mentions may be unhelpfully listed from unrelated areas of the vault - other stories/projects etc.
- The link button is positioned bottom right of each list item, leading to a lot of unnecessary mouse movement when going through a long list of differently sized items.
Proposed solution
- Add a [link all] option at the top of each page/group, and for the top level unlinked mentions group. This will give users control at different levels of granularity and a more efficient workflow.
- Allow a user to set the scope (path) for aliases in the YAML header. This will enable users to limit story bible links to the draft/manuscript pages of the same body of work.
- Reposition the [link] action so that its position does not change after clicking it when the next item shows. This will reduce mouse movement for users who desire more granular control or to review each unlinked mention before linking.
Current workaround (optional)
- Partial workaround: Find and replace can help create links at volume where aliases occur, but it is difficult to avoid aliases within links also being replaced with new links, leading to unusable nested links: [[page|[[page|[[page|display text]]]]]]
- Partial workaround. Open the relevant draft/manuscript folder in VSCode and use global find/replace. Has the same risk of nested links.
- No workaround
Related feature requests (optional)
I got an error when I tried to link to these posts (it is not clear how these links should be created): option-to-always-link-an-unlinked-mention-as-an-alias/48304, single-click-link-for-unlinked-mentions/76141