Logseq has become my latest obsession and quickly replaced my other “ultimate-note-dump” solutions. It has an extremely vibrant community, but (no offense) not always adequate documentation. Turns out, many things one might be looking for have already been implemented, but one only finds out the right way to do them via the community.
For me, one of these things was link aliasing. Let me explain what I mean. We all know that Logseq (similar to Obsidian, Roam Research, and others) supports a wiki-style way of linking between pages. In simple words, referring to a
[[page]] using double square brackets will automatically add a link to it.
The problem I’ve had was linking to a page in the context of a sentence or block of fluent text. So, I’d usually do something like that:
Indeed, not the nicest idea. It fulfils the part of linking to a page, but breaks the fluency of the text.
Turns out, the real solution was right in front of my nose, and I’d never bothered to try it. What if instead of linking to a
[[page]], we do it like this instead:
Every [model]([[Django/Models]]) class in Django has its inner `Meta` class
And indeed, it works like a charm. I no longer need to decorate my text with superfluous links. I can do that as part of the text itself.
Hope this helps others too.
Have something to say? Join the discussion below 👇
Want to explore instead? Fly with the time capsule 🛸
You may also find these interesting
It works, but is a little trickier than I thought at first.
Logseq is the closest thing to event sourcing in note-taking and knowledge management.
Most people using Obsidian prefer using a single vault for all their notes, according to a quick poll. This gives users more flexibility and fine-grained control in organizing their notes. A single vault also contains all of one’s notes in one place - this is especially useful for cross-linking and knowledge discovery.