You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Waypoint has become absolutely essential for having my vault well MOC-ed. I lean on folder structure and let it do the work. However a few of the areas I work on have way too many files in them that even diligent Folder note gardening can’t hide. This becomes an issue when using sub-graphs on the side or just excessive number of links that overcrowd the Graph View. As a result I end up with super-nodes that are far too connected in a way that crowds out gleaning insight from the links.
My wish is to have a “Waypoint - …” file for a few select fields. For example Waypoint - AI) sitting in an AI/ folder with AI.md Folder note. This would allow for AI itself to take on the incoming backlinks and certain important outgoing links and Waypoint - AI would point to everything else AI, I could even make it be The MOC and have AI just take backlinks. I’ve been trying to use #AI with subtags to reduce the number of links, but it’s still way too many, and it’s extra cognitive load + discipline to decide when to link and when to tag for what is essentially the same purpose, and then having to tag-search which is not the ideal way to reach notes.
Perhaps even better, _AI_.md which would sort above the rest of the notes, right under the folders. There are many possible ways I see for accomplishing this in order to reduce too much scanning and thus avoid degraded performance. I don’t know enough about Obsidian or Waypoint internals to say which is best, but here are some ideas:
a list of files through options (least good for users, takes maintenance)
a fixed prefix, such as _Waypoint - (if a just an underscore is too common)
a pair of underscores wrapping a note name that matches the folder name
a designated / configurable #Waypoint tag (probably easier than the next)
a designated / configurable Waypoint: true property
Personally I’d prefer the 3rd or 2nd option as it’s the least maintenance. Underscore-wrapped notes can be just another toggle in options. Maybe with ability of changing it to double-underscores such as __AI__ for people who already use underscored notes.
The text was updated successfully, but these errors were encountered:
Waypoint has become absolutely essential for having my vault well MOC-ed. I lean on folder structure and let it do the work. However a few of the areas I work on have way too many files in them that even diligent Folder note gardening can’t hide. This becomes an issue when using sub-graphs on the side or just excessive number of links that overcrowd the Graph View. As a result I end up with super-nodes that are far too connected in a way that crowds out gleaning insight from the links.
My wish is to have a “Waypoint - …” file for a few select fields. For example
Waypoint - AI
) sitting in anAI/
folder withAI.md
Folder note. This would allow for AI itself to take on the incoming backlinks and certain important outgoing links and Waypoint - AI would point to everything else AI, I could even make it be The MOC and have AI just take backlinks. I’ve been trying to use#AI
with subtags to reduce the number of links, but it’s still way too many, and it’s extra cognitive load + discipline to decide when to link and when to tag for what is essentially the same purpose, and then having to tag-search which is not the ideal way to reach notes.Perhaps even better,
_AI_.md
which would sort above the rest of the notes, right under the folders. There are many possible ways I see for accomplishing this in order to reduce too much scanning and thus avoid degraded performance. I don’t know enough about Obsidian or Waypoint internals to say which is best, but here are some ideas:_Waypoint -
(if a just an underscore is too common)#Waypoint
tag (probably easier than the next)Waypoint: true
propertyPersonally I’d prefer the 3rd or 2nd option as it’s the least maintenance. Underscore-wrapped notes can be just another toggle in options. Maybe with ability of changing it to double-underscores such as
__AI__
for people who already use underscored notes.The text was updated successfully, but these errors were encountered: