bi-directional links

Bi-directional links, also known as backlinks or cross-references, are links that connect two or more pieces of information in both directions. In other words, a bi-directional link allows you to navigate from one piece of information to another and back again.

They can be a powerful tool for building a personal knowledge base and for making connections between related ideas. They can also make it easier to find and access specific pieces of information within a large collection of notes.

Backlinks

link-based note-taking appLink-based note-taking apps are centred around the use of wikilinks. Wikilinks are typically created by surrounding the text with double square brackets. Some examples include but aren't limited to: * Obsidian * Logseq * Roam ResearchFleeting Notes: Google Keep with Backlinks and Easy Sync to ObsidianIf you're a fan of Google Keep, you know how useful it can be for capturing quick notes and ideas on the go. But what if you could take the convenience of Google Keep and combine it with the powerful organization and structure of Obsidian? That's where Fleeting Notes comes in. What is Fleeting Notes? I created Fleeting Notes as a note-taking app that is similar to Google Keep in many ways. It allows me to quickly jot down ideas, thoughts, and to-dos in a fast and effortless manner, and it's acHighlighting from the browser to Obsidian, an alternative solutionOne of the most common ways of capturing content from the web is by highlighting/annotating content. There are many different tools to accomplish this like Readwise, raindrop.io, and Hypothesis. These highlighting solutions are fantastic and have an easy sync with Obsidian. But there comes an issue with processing these highlights/annotations. It's not clear how to utilize or store highlights/annotations especially if it isn't something planned to be used immediately. One key feature of ObsidiaHow I Publish Obsidian Notes for my Landing Page (Next.JS & Tailwind CSS)I wanted to create a website for Fleeting Notes that reflected the interconnected nature of Obsidian, with bi-directional links and interlinked blog posts. However, I struggled to find a platform that met all my requirements: * Support for Obsidian's ![[]] syntax and other basic markdown * Customization using ReactJS * A straightforward publishing process. That's why I built my own system using Next.JS and Tailwind CSS. My ultimate goal was to be able to publish my notes from an Obsidian VaultImprove Note-taking by Organizing Notes like CodeNote organization is very opinionated. There is no shortage of ways to organize notes and everyone seems to have their own method of doing it. Although these methods are great for the short term, as the number of notes grows it becomes difficult to manage notes with these self-made systems. Funnily enough, the very same thing happens to programmers as well. As code gets more complex, it becomes harder to manage code. Now the difference between the two is that poorly managed code has real tangib