Remove these ads. Join the Worldbuilders Guild

Autolinker Upgrade

Feature Upgrade · World management · Created by Bonus Action
open

The Autolinker

I love the autolinker, it saves so much time. However, I've been running into the problem that as my world is connected to a game system, I have made articles with a title that feature a generic word, like 'Life', or 'Magic'. In my case, these are Dungeons and Dragons divine domains, but many generic concepts in other worldbuilding might have run into this issue.
These articles would come up in the autolinker every time the word comes up regardless of context. For example, if I'm writing about a character: 'Her life was marked by tragedy', 'Life' does not have to be linked to the divine domain of life here.  

Making Exceptions

My suggestion is quite simple in theory: Adding a 'do not include in autolinker' tickbox in the 'Preferences' section of articles. That way it would be possible to exclude certain articles from autolinking. I'm not sure how hard it would be on the back-end, but I'm hoping it would be relatively easy to implement.
This feature might also be beneficial for articles that should be public, but not accessed through other articles by clicking through. This feature would make it easier for authors to direct readers in the right direction, or not accidentally expose information directly.

Other solutions

Of course; we could just manualy link articles (and not use the autolinker), or rename the articles that have these issues (in my case from 'Life' to 'Divine domain: Life'). However, in the cases you do want it linked (or shown in a tagged list) I think it becomes rather bulky with a large name. Of course, just skipping them in the Selective replace feature of the autolinker is already an option, but I think it would be great to just click 'replace first of each' (or every single one) and not worry about it.

Priority


I think this feature has a super low priority. Like I stated above, there are a couple of work-arounds and it is definitely just cool to be able to speed up the workflow, but not necessary. if it is hard to implement I'd rather have the devs working on something else. It would be a nice quality of life improvement in my opinion.
Current score

19/300 Votes · +3303 points

Votes Cast