Trust me, I've read every page of Zettlelkasten.de. It's a nice site (and I like their software) but there is no fleshed out examples that I've seen on it.
Again, I get the concept, but I want to see examples in use.
Could you clarify what specifically you have questions about, and/or what docs are perhaps slightly better (or worse). Or documentation for other concepts you've found useful?
Regards Zettlekasten itself: the key notion to me is simply capture and reference. Those are the dual-natured heart of the system.
The rest is just mechanics. Important mechanics, in cases, but mechanics all the same.
Everything I’ve read on Zettelkasten has been the equivalent of trying to learn to program by reading a reference book. Sure, I could technically learn Python by reading an exhaustive list of methods, classes and operators, or I could pickup a book which explains key concepts through an example project and examines the syntax through a specific context.
I learn best by example, personally, and I’ve never seen good examples on this topic myself.
I think the point most guides overlook consists of the internal semantics of using a Zettelkasten, Luhmann essentially used it to create a paragraph (Zettel) & subchapter (Zettel Sequence, but note they of course sometimes he'd not manage to fit an entire paragraph on one Zettel due to margin limitations) branching & branchable, recursively self-referential choose your own adventure hypertextbook, from which he'd then generate regular textbooks. Hence why he said that his books basically wrote themselves — to write a book, he'd 'just' enter the Zettelkasten, and copy out everything he'd already written there on the topic, picking between branches & branchings as he went back, forth & side-to-side within it. Hence why if one looks close, one can find Luhmann seemingly self-plagiarising paragraphs from books he'd previously written. I suspect a similar mechanic sits behind the (in this sense very ignorant) accusations of self-plagiarism against Slavoj Zizek.
As such, one might wish to instead consider using Hypertext Fiction tools for creating a Zettelkasten, such these two (proprietary software, Mac OS X only, unfortunately):
And secretly use the patching patches feature of pijul.org in the background so version control actually becomes sanely doable, throw in elastic tab stop support, and maybe an entire kitchensink in which someone let a mixture of ChrysaLisp, SmallTalk, Hazel, Scala 3, /r/nosyntax, Inferno, RINA, GNUnet, & every single proof assistant and theorem prover sit for a tad bit long, and then MAYBE we can stop living in the dark ages of computing.
Tinderbox was something I paid for (and wanted to love) but it was just too bloated and buggy. The creator's stance on "artisan software" is intriguing, but frankly the software doesn't put him in a good light. I'm willing to pay good money for good software, but $180 for software that feels like it's an open source alpha project is annoying, especially software that is meant to contain massive amounts of connected data.
I sat in the same boat as OP and that page wasn't that helpful. It's starts backwards with
- How many of things I know nothing about should I have.
- Don't use this aspect in the thing, use the other.
…
And every article is a text wall of minutia addressing questions which are going to be relevant later on, but are just information overload if you try to understand What is it?
