Obsidian Journey Plugin Versions Save

Issues Fixed

Icon (simplified) now appears equal on light and dark modes:

Fixes: https://github.com/akaalias/obsidian-journey-plugin/issues/7

New Features

Automatic Linking

If set, will turn titles in the list into links to their respective note. (Off by default)

Example output (All note titles are links):

Automatic Transclusion

If set, will automatically create transcluding links for you ('![[note]]' instead of '- [[note]]') (Off by default)

Example output (All links are transcluded):

Bug Fixes

Fixes mutated vowel/umlaut-tag problems #6

New Features 🎉

Based on your amazing feedback and ideas, you now have the following new features available:

Exclude Folders Feature

Allows you to set a list of comma-separated folder paths (e.g. "Daily Notes/, Attachments/") that will be excluded during your search.

Auto-complete Search Feature

Search your starting and ending notes by simply starting to type in the name.

Communication

Reporting issues

Please use https://github.com/akaalias/obsidian-journey-plugin/issues to share bugs and issues you find!

Backlog

I've created a public backlog which will allow you to see the progress on features. Prioritisation will come from voting in the group and at my own discretion.

https://trello.com/b/ICKWjoBu/obsidian-journey-plugin-backlog

New features

• High-contrast results

Based on EdElgar's request for higher contrast when reading the result list, you can now toggle on 'high-contrast' in the settings. This will give results in black and white:

At the heart of it, this plugin finds the journey between two notes in your Obsidian vault. Watch the quick demo below to get an idea:

What features are included in this release:

Based on your feedback and comments, I realized that there are many different ways to go on that journey and so I've created a bunch of features you can toggle on or of to your liking.

These features are like preferences you can give your navigation-system in your car. Maybe today, all you care about is getting from A to B quickly. Maybe tomorrow, you have more time to "take the scenic route." I want you to be as flexible as possible.

• Feature 1: Use "Forward-Links" (Enabled by default)
• Feature 2: Use "Back-Links" (Enabled by default)
• Feature 3: Using Tags (Disabled by default)
• Feature 4: "Take the scenic route" aka Avoid MOCs (Disabled by default)

Because each feature has an impact to whether the plugin CAN FIND or CANNOT FIND a path between your two notes, I want to demonstrate what each does as simply as possible.

So, let's start by imagining this very basic vault with 4 notes. "Note A", "Note B", "Note C" and "Note D"

• A links to B
• B links to C
• C shares the same tag as D

Feature 1: Use "Forward-Links" (Enabled by default)

Links are basically one-way streets from one note to the next. That means the plugin will show you only a path IF a forward-linked path exists but it won't show you a path that goes "against" the one-way street.

With the example and this feature turned ON, the plugin will...

• Successfully find you a path from A to C (Via B)
• NOT find you a path from C to A because that would be against the one-way street

Feature 2: Use "Back-Links" (Enabled by default)

This is basically the inverse of using "forward-links". With this feature, you navigation system will find ONLY paths that are based on going against the one-way streets.

With the example and this feature turned ON, the plugin will...

• NOT find a path from A to C because there are no back-links to follow
• Successfully find you the path from C to A (Via B) because the back-links point that direction

Feature 3: Using Tags (Disabled by default)

Thank you alltagsverstand for the idea which I had not thought of and which resonated with many of you.

As the name suggests, Tags can now also be paths between notes.

With the example and this feature turned ON, the plugin will...

• Successfully find the path from C to D (C -> #tag -> D) and from D to C (D -> #tag -> C)

If I now have Back-Links and Forward-Links enabled as well, I can now find the path from:

• A to D (A -> B -> C -> #tag -> D)
• D to A (D -> #tag -> C -> B -> A)

Note that this feature is disabled by default.

Feature 4: "Take the scenic route" aka Avoid MOCs (Disabled by default)

One of thoresson's many ideas that turned out to be really, really useful when I started to pressure-test finding cool paths.

Avoid Y (perhaps a tag used for MOC and other structured notes so that only atomic notes are included in the journey)

If turned on, this feature will exclude finding a path via MOC notes and help you "take the scenic route" instead. With this feature, you avoid passing through the "big city" (aka MOC) and instead find a path less traveled.

In the following example, with this feature turned ON, the path from A to C would be:

• A -> Foo -> Bar -> C (instead of A -> MOC -> C)

"How many links make an MOC?"

A sub-feature for "taking the scenic route" where you can define at what amount of links inside a note makes it an MOC to avoid.

A huge shout-out to thoresson, alltagsverstand, Thecookiemomma, cestvrai, matteor, Danashafir, EhuddRomero, I-d-as, osgav, Erick_James_Dodge, 3mbry0, Klaas, ryanjamurphy, EdElgar and Daveb08 for helping making this awesome for everyone!