There is pretty straightforward instructions from the author. If your are on Windows, install the tool with Chocolatey (and install Chocolatey, if you don't have it).

Now, all your links will look something like this [[]] . This is hard to read and a bit cumbersome, so here's how I style it (again, very subjective):

1. I use italics for the title after the link. This makes it stand out more in text and clearly delimits the extend of the title in texts.
2. I use the following custom CSS to shrink the [[]] part down to [[↗]] until you hover over it. You can still click it, but it renders much less obtrusively. The whole thing is sort of an ugly workaround, and I would love to get more options for this in Zettlr itself (also being able to link to different sections and maybe make annotated wikilinks), but this is the best I could find for now.

​

#editor .cm-zkn-link:not(:hover),
body.dark #editor .cm-zkn-link:not(:hover) {
    font-size: .01em;
    visibility: hidden;
}
#editor .cm-zkn-link:not(:hover)::after,
body.dark #editor .cm-zkn-link:not(:hover)::after {
    font-size: 100em;
    content: '↗';
    visibility: visible;
}

With this, a Zettel might look something like this:

https://preview.redd.it/csctr6s2rda71.png?width=1010&format=png&auto=webp&s=9106322d5ced20c6921466c52136b48468b7f75e

backlinks and graph analysis

A much-requested feature is backlinks (links from a Zettel to all places that link to it). Zettlr hasn't implemented this yet, so I'm using the note-explorer script by C. Daven to insert them. Every once in a while, I run

noteexplorer -b "___" ..\ update-backlinks

to generate backlinks for all files. I modified it to use ___ as the delimiter of the backlink section, but anything should work.

I also use the script to check for "floating" Zettel (i.e. with no link going in or out, thus not connected to the rest of the Zettelkasten) and modified it to update the filenames based on the YAML title as specified above.

This still doesn't give you the full graph experience, but it's good enough.

tags

While tags are a nice feature, I don't really think they are necessary for a Zettelkasten – or all that useful. In a text, if you want to mention an overarching or related topic, you should really link to a Zettl about it. The only place where I think they could be useful in the content of a Zettel is when you want to link to something you haven't created a Zettel for yet. As Zettlr sadly doesn't allow linking to placeholders, you can use tags to keep track of what topics you might want to open a Zettel to later on and then insert links to it when you've actually written it. However, even in this instance, it might be better to just link to an empty Zettel instead.

Where tags really are useful is metainformation. Using tags for meta info allows you to quickly find Zettel independent of their relationship established by links and their content. I use this to e.g. collect all Zettel that belong to a certain lecture for reviewing, or to mark all Zettel that needs an overhaul. Conveniently, you can include these tags as keywords in the YAML-header, where there nicely separated from the content of the Zettel and are immediately showing you what meta-information this Zettel has (you can see that in the image above).

lookout

That's it! That's how I implement my Zettelkasten. Feel free to ask questions if anything is unclear, or offer suggestions from your experience.

Also, I implemented a python script that extracts marked paragraphs from Zettel as Anki flashcards, which is really handy to study lectures with. If anyone is interested, I might share that in the future.

I started with Zettlr in the Autumn, and have been using timestamp IDs at the front of the filename. But, I've started rethinking this, much due to my own tool NoteExplorer, in which I'm currently developing a feature to rename files and all links pointing to that file. With better tooling, the ID isn't as useful, unless you want to link to specific files from outside of your Zettelkasten.

My new tool is called NoteExplorer, and can also do some network analysis.

Source: (1) A personal knowledge management and sharing system for VSCode - Foam. https://foambubble.github.io/foam/. (2) A personal knowledge management and sharing system for VSCode. https://github.com/foambubble/foam. (3) Loam - Visual Studio Marketplace. https://marketplace.visualstudio.com/items?itemName=ciceroisback.loam.

You should have a look at Foam: https://github.com/foambubble/foam

I started using Foam[0] a few years ago, but the more I used it, the more I dropped all the tedious bits, and it became nothing more than a big, evolving markdown repo.

When I switched from vscode (back) to vim, it has worked as well or better than it did before. I follow my own rules. I like the Zettelkasten idea of one idea per card, but if I put more related things in the same .md file, that's OK. I didn't like the flat directory structure, and so I have dirs organized by category. My /bar directory is inside my /cooking directory, and for whatever reason, that makes sense to me. Ripgrep doesn't care, and I always find what I'm looking for.

This markdown hierarchy, that still lives in a repo called "foam", has become indispensable to me.

[0] https://github.com/foambubble/foam

Probably use foam https://github.com/foambubble/foam

So I switched to FOAM and it's just clean & organized markdown files in a git repo. Self host a code server instance and I can reference it without installing something to the work machine.

Recently I started to configure my digital garden. Foam is a good option, Hugo Doks, No Style Please, Git-Wiki, Researcher, Thinkspace, and other themes are good for zetteltasken pages.

I use foam and VSCode and regularly am wow'd with what I am having it do next. I feel I am still just getting started too.

I've wondered about using obsidian with foam as a web editing fallback.

Since the data store is markdown and can be synced with Git, you can already work with an Obsidian vault using Foam in VSCode. I do.

You do need to align some options in each, such as file naming, a header, a particular style of links, and ensure frontmatter behavior. All necessary settings exist.

https://foambubble.github.io/foam/

https://github.com/foambubble/foam/issues/46

This supports basic static file and links functionality, not extended data tools etc., of course.