Explain the problem as you see it
Sometimes I think of @[[tagging this phrase]] and making it an alias to @[[tags]].
The problem is that I need to firstly type in @[[tags]] and then hover over it >> "Edit alias" >> type in @[[tagging this phrase]]. Which is the inverse of the workflow.
And that would be ok if the alias was stored for future use - except it wasn't. Meaning that in future if I want to reuse this alias by typing @[[tagging this phrase]] again, it wouldn't automatically allow me to tag @[[tags]].
Why is this a problem for you?
It breaks my chain of thought because I'm forced to start thinking about how to create nodes and then create aliases, which is quite disruptive and doesn't "flow".
Suggest a solution
1) I suggest making it more intuitive. For example, if I'm typing @[[tagging this phrase]] - when the dropdown menu comes down, there should be an option to use it as an alias for a new or existing node. Maybe if I "tab" it turns into an alias which can seek a connection to a node?
2) I suggest for aliases to be remembered. If I type @[[tagging this phrase]] in future, I would want it to automatically have the option to connect to @[[tags]] which I had connected to in the past; Yet, I would also want to have the option to change it to a new node if I wanted.
1 Comment
Or in the node, have a system field called "Aliases". When @ referencing the node, the node name and all aliases for it show up.