![]() You can export notes to different formats, and more. On the other hand, Zettlr could fall into the category of an authoring tool for end products, such as a report, a paper or even a book. I like the simple interface that does not get in the way. My favorite to use on a daily basis is Obsidian It may sound like a minor feature, but it is great to quickly find orphan notes, put several together and understand our thoughts by proximity. They both support quick links with the wikilink format, although Zettlr offers a bit more of configuration on how they look like (adding text, referencing by title, etc.) Obsidian offers bidirectional links, and a network graph to see how notes are linked to each other. Obsidian is more minimalistic than Zettlr. It is worth noting that since files are stored locally with a common format, there's no risk regarding the continuity of my project in case either of them disappears from one day to the other. Although it is free to use with some premium features. Is not open source and probably will never be. I have actually used parts of the code of Zettlr to understand how to parse markdown and render this website. But they are different to each other and that is what I wanted to discuss.Ĭhoosing technology based on their incentives I have explored different programs, and none reaches to the level of either I know this is not for everyone, but I am confident it is the same workflow for ![]() The kind of note I would take on a phone is the kind of note I take on paper. I take notes always when I am at my desk. I don't need to take notes on my phone and have them ready on my computer. The first few requirements are based on my own workflow. No forcing of organizational hierarchy or structure Supports easy linking (such a as wikilinks) In a format that guarantees long-term compatibility (such as Markdown) After experimenting for some time, I narrowed down the list of requirements for the software I use to take notes: I assume the general idea is easy to implement in other static site generators., I had to look around for tools I felt confident using in the long run. It’s not difficult to adapt the above code to also look for implicit links, but it reintroduces semantic difficulties (will “Castlevania” do or is “Castlevania: Aria of Sorrow” needed, and what about that colon?). That is, implicit backlinks are ignored, a feature of Obsidian that might or might not be of interest. One obvious disadvantage is that, if you don’t mention one game in the article of the other (or the other way around), the articles will still not be linked, since we search for the (relative) URL, not the name of the game. The result can be viewed in the sidebar of for example the Hollow Knight review under “Related Posts”, which has links to The Messenger, Castlevania: Aria of Sorrow, Guacamelee, Castlevania Advance Collection, and Super Metroid-all similar games that are not linked by manually adding tags but automatically by collecting backlinks! ByDate.Reverse) should be added in the end, not in the beginning: that list is much smaller. ![]() Since we are only interested in “any” match, set it to 1. findRE has a third parameter which helps stopping to look for more matches after the xth one.Why? Because I want to show the relevant backlinks first, but if there are none, I’ll be content with a few regular links to related games. I keep backlinks and forwardlinks in a separate list and merge them in the end.Why? Because the is something like /games/switch/toem/, but when I link it in an article, I usually leave out the trailing slash, resulting in no match. On the bottom of each Brain Baking post, the following code finds the first three related posts based on the intersection of tags, excluding the current page: The same is true for tags, which traditionally are used in Hugo-powered blogs to find related articles. I’ve written before about reducing friction and automating metadata keys and how it facilitates writing. After thinking things through and a thorough refactoring attempt, this is now automatically deduced based on the folder name (e.g. For example, on my retro gaming site Jefklak’s Codex, I categorize each game entry by platform-a platform metadata key that had to be manually entered. An average blog engine has you sweating and coming up with needless details, such as tags and other metadata. A great blog engine removes friction and pushes you to write more.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |