📚 Agora node [[zettelkasten]] ☆
Agora nodes contain community contributions with titles or topics that match your search. x
📜 File zettelkasten.md by @flancian ☆ 📎 ️🔗 ✍️ ⛶

Zettelkasten§
🕒 Last updated 2026-03-26 23:53:53
📜 File zettelkasten.md by @vera ☆ 📎 ⛶
  • The notes are numbered hierarchically, so that new notes may be inserted at the appropriate place, and contain metadata to allow the note-taker to associate notes with each other. For example, notes may contain tags that describe key aspects of the note, and they may reference other notes. The numbering, metadata, format and structure of the notes is subject to variation depending on the specific method employed.
🕒 Last updated 2022-01-28 17:25:08
📜 File zettelkasten.md by @neil ☆ 📎 ️🔗 ✍️ ⛶

zettelkasten§

See [[A System for Writing]] for the best intro.

Zettelkasten at its simplest:

  • One idea / thought per note.
  • Link those that inform or speak to one another (giving context for why).
  • As trains of thought develop that interest you, bring those ideas into a structure note or writing doc where you can explore the ideas and their connections further.

Rinse and repeat.

– Bob Doto 📿 🗃 🚩: "Zettelkasten at its simplest: …" - PKM.social

Literally, "box of notes". But with a process around that.

He wrote only on one side of each card to eliminate the need to flip them over, and he limited himself to one idea per card so they could be referenced individually.

– How To Take Smart Notes: 10 Principles to Revolutionize Your Note-Taking and …

-Zettelkasten — How One German Scholar Was So Freakishly Productive

It feels a bit like the philosophy of [[tiddlers]], to me.

The purpose of recording and organising information is so that it can be used again. The value of recorded information is directly proportional to the ease with which it can be re-used.

– Philosophy of tiddlers - TiddlyWiki

Notes / steps§

  1. Literature notes
  2. Reference notes
  3. Permanent notes
  4. Review and repeat
  1. Capture ideas in the form of fleeting and/or reference notes.
  2. Turn these captures into individual main notes.
  3. Establish connections between the ideas recorded in these main notes.
  4. Keep track of developing trains of thought in hub notes, structure notes, and indexes.
  5. Turn these trains of thought into writing

– [[A System for Writing]]

Digital Zettelkasten§

I use [[org-roam]] for this.

Does it make sense to have a timestamp in the filename?
🕒 Last updated 2025-06-23 01:54:06
📜 File Zettelkasten.md by @binnyva ☆ 📎 ⛶

Zettelkasten§

Zettelkasten is a note taking process and a knowledge management system. It’s really good for researchers, academics who want to create content - but also good for people trying to learn.

Rational§

When learning reading and re-reading is useless for understanding. This is called the [[Mere-Exposure Effect]]. What helps is trying to explain what you learned - that will show all the gaps in your understanding. Taking notes is a simple way of doing it. Micro testing.

When taking notes, you should [[Capture Understanding - Don’t Quote]] - don’t copy the text as is. This will show you how much you understood - and what the gaps are.

Process§

1. Fleeting Notes§

When consuming content - a video, podcast, article or books, take down fleeting notes. These are temporary notes that serve as memory reminders when creating the actual notes.

2. Literature Notes§

You can convert these notes into a better formatted version called literature notes. It will be a summary of the entire content. Keep it short, be very selective and use your own words.

3. [[Permanent Notes in Zettelkasten]]§

When you have finished the content(or at some smaller point if you are reading a book or consuming something big), you go thru these fleeting notes and write down the main concepts that are presented. These are the permanent notes. Make sure the permanent notes meet the following criteria

  • Write one idea per note - but as complete as possible
  • Write as if you are writing for someone else - use full sentences, show sources.
  • Be precise, clear and brief
  • Should be understood even if you don’t know the context it was taken from.

Think of how the new notes are connected to the other existing notes in the system…

  • How does this idea fit into what I already know
  • What does this idea mean for another idea I already have
  • Does this add to, contradict or explain another idea I already have

If the new idea is connected to an existing idea, link out to that idea from the current one. After a while, this will end up being an interconnected web of ideas.

Tags§

#zettelkasten #permanent-notes
🕒 Last updated 2021-03-28 22:31:16
📜 File content/Zettelkasten.md by @houshuang ☆ 📎 ⛶
🕒 Last updated 2021-03-28 22:31:14
📜 File zettelkasten.md by @vera.wiki.anagora.org ☆ 📎 ⛶

A Zettelkasten is neither a neatly structured filing system for notes easy to access nor a turmoil deep sea generating ideas out of the ununderstandable chaos. There are three layers in my archive which emerged from the years of working with the Zettelkasten Method. I didn’t plan them in advance. It rather was an organic process.

A [[personal knowledge management]] process.

The core of the process revolves around two collections of notes - [[Reference Notes]] which summarise source material and include a link to the source, and the collection of [[evergreen notes]] which are written in the interpretive part of the process.

The 20th-century German sociologist [[Niklas Luhmann]] managed to publish 70 books. He credits much of his success to his Zettelkasten, or "slip box."

Luhmann, N. (1992). Communicating with Slip Boxes. In A. Kieserling (Ed.), & M. Kuehn (Trans.), Universität als Milieu: Kleine Schriften (pp. 53–61). [http://luhmann.surge.sh/communicating-with-slip-boxes page]

see also [[Zettelkasten project]]

below content stolen from [https://zettelkasten.de/posts/three-layers-structure-zettelkasten/ here]

Bottom Layer: Content§

The first layer of course consists of content notes. I write, I research, I get ideas. All of that goes into my archive. The full text search and the search for tags are sufficient enough to handle a smaller archive. At this stage it is only natural to stress the importance of tags. You are using them frequently and they serve as important entrances into your archive.

But after a while, you won’t be able to keep up. When I search for tags I get a couple hundred of notes. I have to review them to connect a note to some of them, or get a grasp of what I wrote and thought about a specific topic.

Naturally, a need to organize the archive arises at this point. I can’t remember how many notes I had when I experienced this. I introduced hub-like notes when I had between 500 and 700 notes. 1 I gave myself an overview of the most important notes on that topic.

It must have been between 1000 and 1500 notes when this became too much to handle. I needed more structure. With every additional note I continued to lose my grip on the archive. I wasn’t very concerned because Luhmann, the godfather of the Zettelkasten Method, never had a grip in the first place. But I thought: I have a big technical advantage over him. I need a grip.

Then structure notes emerged.

Middle Layer: Structure Notes§

My archive became opaque like the sea: You can see a couple inches into the deep but you know there is much more that you can’t access. You can dive deep, but still you just see a couple of inches at any time. Therefore, I thought of it in terms of unexplored territory for which I need mapping methods and such.

I started with structured lists to have tools to get a precise idea quickly how a certain space in my archive is structured. (similar to what Luhmann had with his hub notes, by the way).

Now, I am at a point where my structure notes embed the structure itself. Take a look at one of my structure notes:

They look much like a table of contents. It’s because they are tables of contents. A table of contents is a structured set of chapters of a book, a set with hierarchy and order. Of course, a book’s page sequence is ordered according to the table of contents for the reader’s convenience. A structure note doesn’t need to adhere to any didactic needs or any needs other than yours.

In the Zettelkasten there are at this point two layers:

  • The content. Tiny, tiny bits of content.

  • Structure notes. Tables of contents.

Structure notes share a similarity to tags: Both point to sets of notes. Structure notes just add another element. They are sets with added structure. This added structure provides a better overview and adds to the utility of the archive.

Top Layer: Main Structure Notes and Double Hashes

After a while, I did not only have structure notes that structure content notes, I also had structure notes that mainly structured sets of structure notes. They became my top level structure notes because they began to float on the top of my archive, so to say.

My structure note on human movement is a perfect example of it. First, I wrote a lot about training. The training structure note linked to strength training, endurance training, sprint training, strongman training, mobility training, and more. But after a while a couple of topics didn’t fit into this space. What about physical work like wood chopping or the whole space of non-movement (like chronic sitting)? The topic broadened and I found a new umbrella: Human Movement. This structure note just keeps on floating on top. It is like the tip of an iceberg. No matter how much water freezes and is added to its body, the top stays on top.

Another type of top-level structure notes are the one I design in this manner right away. I worked a lot on the topic of self-worth from various perspectives (even from the perspective of cardinal sins; the perspective is broad!). The structure note is tagged with a special tag: ##self-worth. If I search for #self-worth (note the single hash!) I get all the notes that deal with this concept but with a double hash I go directly where the money is in my archive: The top-level structure note.

The difference between these two kinds of top level structure notes is in how they turn out to become top level: Human Development emerges because of the structural changes in my archive, while the one with ##self-worth is marked as a top-level structure note because I designed it to be a top-level note right away. (I mark the human development note with a double-hash, too).
🕒 Last updated 2021-11-06 23:04:06
📜 File content/pages/Zettelkasten.md by @wilde-at-heart ☆ 📎 ⛶

What is a Zettelkasten?§

In German, Zettelkasten means "slip box." It is both a method of [personal knowledge management]({{< ref "personal knowledge management" >}}) and a physical (or digital) system you maintain. The method was popularized by German scholar Niklas Luhmann who used it as a "conversation partner" to help write hundreds of articles and books. To create a Zettelkasten, you need two compartments: literature notes and Zettels. Literature notes are just bibliographic information. Niklas Luhmann wrote the citations of resources on index cards. I keep my references in Zotero. Zettels are what you will see in my digital garden as 🌳 evergreen notes. They are not notes I would take while reading something. Rather, they are insights and my own thoughts on what I read or in general. Zettels should be one idea, called an atomic idea. Remember: Niklas Luhmann wrote his Zettels on index cards. Although they are a tidied up atomic idea, they are not immutable.

As you write Zettels, you create links between them. The more Zettels you have, and the more links exist between them, the easier it is to see where clusters of ideas form. This is the "conversation partner" aspect of the Zettelkasten. When clusters form, it shows you what you’re interested in and where you have a lot of information already created. From there, you can combine the Zettels and use them to express something larger and more complex.

You can learn more about Zettelkasten at zettelkasten.de. I also like how Bob Doto explains the Zettelkasten.
🕒 Last updated 2022-06-26 22:52:23
📜 File zettelkasten.md by @agora@botsin.space ☆ 📎 ⛶
🕒 Last updated 2023-05-26 03:08:46
📜 File Zettelkasten.md by @agora@botsin.space ☆ 📎 ⛶
🕒 Last updated 2023-07-10 09:46:24
📜 File zettelkasten.md by @an_agora@twitter.com ☆ 📎 ⛶
🕒 Last updated 2022-11-05 23:01:52
📜 File Zettelkasten.md by @an_agora@twitter.com ☆ 📎 ⛶
🕒 Last updated 2022-11-02 00:35:23

Loading pushes...

✨ AI Synthesis Mistral Gemini ChatGPT Claude x

Expanding this section will automatically generate an AI synthesis of the contributions in this node.

🌌 Agora context for [[zettelkasten]]

Rendering context...

📚 Agora node [[20200617233727 zettelkasten]] (pulled by the Agora)
📜 File 20200617233727-zettelkasten.org by @ryan ☆ 📎
#+title: zettelkasten The Zettelkasten method is a method for note-taking and resource management. It is what I’m trying to do with all these org-roam files, but I feel like I’m failing! Notes in Zettelkasten should be: - atomic :: notes should pertain to one specific topic - connected :: there should be clear lines between related notes I need to start using org-roam more for personal notes as well as knowledge notes. * Resources - [[https://zettelkasten.de][Zettelkasten knowledge and info management • Zettelkasten Method]] - [[https://zettelkasten.de/posts/create-zettel-from-reading-notes/][Create Zettel from Reading Notes According to the Principle of Atomicity • Ze…]] - * Tools - [[https://obsidian.md/][Obsidian]] * Ways to improve use of Zettelkasten with Roam - Capture fleeting notes (optional) - Connect literature notes (notes on books, articles, etc.) with ideas and reflections - Create reflection, “argument”, notes. Use the connection between notes to generate new ideas (see “permanent notes”) - Note to self: you’re already doing this! Notes like “Marx” etc. are permanent notes! You just need to be willing to actually fill them out and notice when they interest you! :)
🕒 Last updated 2026-03-03 19:54:56
📚 Agora node [[20230526T045952 emacs__emacs_org_workflow_zettelkasten]] (pulled by the Agora)
📜 File 20230526T045952--emacs__emacs_org_workflow_zettelkasten.org by @oceane ☆ 📎

Emacs is amazing. Reading its info pages does feel like homework, but as an autistic person I precisely need explicit instructions on how to use the software.

Emacs lets me do:

  • task lists,

  • spreadsheets,

  • blog posts,

  • assignments,

  • personal documents,

and export them to:

  • PDF,

  • Markdown,

  • ODT,

  • etc.

It also lets me insert academic citations by setting the BibLaTeX and CSL engines according to the file format in which I want to export.

For example I write many documents intending them to be blog posts, only to figure out that they're long rants about social media, abuse, and my own life, but I can keep them as documents and eventually print them to show them to my partner. Without that my blog would probably be in a much worse state, or drafts would hang around in a remote database that's hard to export and could honestly be deleted overnight (even if Matt and his team are great people).

It also works with local files which is super important to me because I've had and still have an unreliable internet connection, and I just don't want to have to care about it. With Emacs I can work at a 16KB/s capped bandwidth for a few days without even realizing it. (This is a lie, I need to run Javascript code every few hours.)

🕒 Last updated 2023-05-27 01:58:45
📚 Agora node [[collaborative zettelkasten]] (pulled by the Agora)
📜 File collaborative-zettelkasten.md by @neil ☆ 📎 ️🔗 ✍️

collaborative zettelkasten§

Collaborative [[zettelkasten]].

See [[Bob Doto]]‘s article for some thoughts: [[How a Collaborative Zettelkasten Might Work: A Modest Proposal for a New Kind of Collective Creativity]]

It is a good template for [[knowledge commoning]]. And to my mind exactly the [[Agora]] provides.

It strikes me that if one were to work on a [[collaborative zettelkasten]], then [[hub notes]] would be quite key. As a means to discover main notes.

It’s very unlikely people would use the same titles for main notes, so hub notes become the, well, hub from which you find other’s views on a topic.

This reminds me of something [[Bill Seitz]] said once in relation to [[twin pages]] and [[sister sites]]…. I wonder if I can find that again.

Something like this, but I think somewhere it’s even more explicit http://webseitz.fluxent.com/wiki/SmashedTogetherWords.
🕒 Last updated 2026-07-02 22:17:33
📜 File collaborative zettelkasten.md by @anagora@matrix.org ☆ 📎

Very Agora adjacent.
🕒 Last updated 2026-04-06 16:06:21
📚 Agora node [[different types of notes in zettelkasten]] (pulled by the Agora)
📜 File Different Types of notes in Zettelkasten.md by @binnyva ☆ 📎

Different Types of notes in Zettelkasten§

Fleeting notes§

They are simple reminders of information or ideas that will need to be processed later on, or trashed.

Literature notes§

Brief annotations on a particular source (e.g. book, website or paper), that you’d like to access later on.

Concept notes/Permanent Notes§

This require much more care in authoring: they need to be self-explanatory and detailed. You’ll have to paraphrase the source material to create this. [[Capture Understanding - Don’t Quote]]

[[Thinking in Zettelkasten]] [[Paraphrasing to Remember]] [[How to Take Smart Notes]]

Tags§

#zettelkasten #notes
🕒 Last updated 2021-03-28 22:31:16
📚 Agora node [[how i use the logseq readwise plugin in my zettelkasten]] (pulled by the Agora)
📜 File content/pages/How I use the Logseq Readwise plugin in my Zettelkasten.md by @wilde-at-heart ☆ 📎

image.png

The above image is the visualization of my Logseq graph, at least as of June 26th, 2022 at around 3:00 PM EDT. I know it’s not as pretty or big as some others you may have seen, but I think it’s a great way to see how I use Logseq, its linking capabilities, and its integrations.

You’ll see some clusters there in the center. That represents the reference notes, topic tags, and main notes of my Zettelkasten. Some of the bigger nodes are reference notes because Logseq brings in the Zotero tags, and I create an author page for each. That messy web dead center is the majority of the main notes. I don’t have enough to create super visible hubs, but it makes me happy that those notes don’t create the "node with spokes" structure that the reference notes have.

Okay, so what are all the other notes floating aimlessly around the messy web? That’s a great question.

Those are the highlights I’ve taken in various web articles and e-books as well as tweets and Twitter threads I’ve saved. They’re brought in through the official Logseq Readwise plugin.

What is Readwise?§

Readwise is a read-it-later service which imports the highlights you take in other websites and apps. For example, any highlights you make in a Kindle book will be sent to Readwise. You can also manually enter highlights or take pictures of physical books to highlight. Once highlights are in Readwise, it prompts you every day to review highlights using spaced repetition.

Why use Readwise?§

I admit to having been skeptical when I first heard of Readwise. I’m not a student, and I don’t feel the need to memorize stuff I read, especially when I’m reading for fun. The only reason I gave it a go was because I got a free annual subscription through the Building a Second Brain course I did. I started using it, and I liked it well enough to keep using it. It’s fun to review highlights from books, web articles, and even tweets I haven’t visited in a long time. Still, just revisiting highlights isn’t meeting any need of mine, at least not one I would pay for.

However, what turned Readwise into a crucial part of my workflow is its ability to export highlights to other apps and services. In addition to reviewing highlights in the app every day, I also have those highlights in my note-taking apps to search and use. I used the Evernote integration for a while, but I don’t really do thinking and creating work in Evernote. Evernote is my filing cabinet. I can full-text search and bring highlights up, but then I have to move those notes around, copy/paste, duplicate, whatever, if I want to use those exact quotations in something. I can’t easily connect them to anything.

Then, I got brought on to test the official Logseq integration.

Logseq Integration§

I mentioned that I use Evernote as my filing cabinet in my "second brain." My other primary tool is Logseq. To quickly introduce it: Logseq is a free, open source outliner and note-taking program which prioritizes local files and privacy. It exists in the same type of app as Roam Research and Obsidian, which allow you to connect notes through backlinks. Logseq, like Roam Research, allows you to reference and embed at the "block" level, not just the page level.

The ability to reference/embed at the block level is what makes Logseq work so well with Readwise. For example, one thing I love about Readwise is that it can save Twitter threads. I used to hate bookmarking the first tweet in a thread, or even bookmarking every single tweet in the thread. In Readwise, I can find that thread and review it, but the individual tweets will be split when doing a daily review. I often review tweets out of context with the rest of their thread. In Logseq, however, Readwise creates a new page for each larger work a highlight is in –– a page for each book you have highlights in, for each article you have highlights in, etc. And for twitter threads, it creates a page for that entire thread.

And each individual highlight has its own block on that page, allowing me to embed and reference it when needed. The highlights don’t exist out of context of their larger work, but I can still use them individually in a way that is linked back to the larger context.

Tweet highlights in Logseq

The integration also creates page links for the author of the larger work and the category (but I remove the category link). It brings in any tags you’ve made in Readwise for the larger work and the individual highlights and any notes you’ve made for each highlight. Finally, it provides external links to the original source if applicable, including links to individual tweets and Kindle locations.

My configuration§

Before I walk you through the parts of my workflow which include Readwise, I want to explain my setup and configuration. My setup is not complicated, but it is not the default, either.

There are several options to configure. For example, you can automatically sync new highlights when you open Logseq. I don’t do this because highlights are only as good as their original page metadata, and I often have to change authors in Readwise. For Logseq in particular, I have to make sure titles don’t contain forward slashes because forward slashes will create namespaces. Disabling autosync gives me time to clean up any metadata before I bring it into my graph. You can also choose to resync deleted pages. I turn this on when I notice some bad metadata or formatting that needs fixing, but I don’t have it on as the default.

Screen Shot 2022-06-26 at 2.01.43 PM.png

When you click "Customize" for formatting options, you have several more options to configure. I choose to leave on "Include Highlight Location," and I turn on "Use Custom Formatting."

Screen Shot 2022-06-26 at 2.02.48 PM.png

When you turn on Custom Formatting, you can change the template Readwise uses to create your highlights pages.

The first is the page title. I am fine with the default because having (highlights) in the title provides an easy way to search and filter without creating a giant page node in my graph.

image.png

Then we have page metadata. I change the default in two ways. The first is that I put quotation marks around the full title value. Otherwise, multiple pages will be created if the title has a comma in it. However, this default may have changed by time of publication or sometime after. I also remove the tag from category. I don’t want a giant cluster in my graph, and I don’t need to see every source I have that’s a book. Some people might, though! This is just my preference.

image.png

Readwise creates a header to nest highlights under. I remove the backlinks from where it says Readwise because I don’t want a giant page node in my graph view. That is a connection that isn’t useful to me, but it might be for you.

image.png

For the actual highlight, I don’t change anything. I would like to make the Tags a block property, but I’m not skilled enough to figure that out. I edit as needed.

image.png

Finally, there’s the sync notification. Because I haven’t created a Readwise page in the highlights header, there’s no place for this notification text to go. I just leave it as the default.

And, like with other Readwise exports, you can choose to select specific items or sync everything.

Workflow§

I use Logseq as my digital [Zettelkasten]({{< ref "Zettelkasten" >}}), and my workflow is fairly traditional. With a focus on how Readwise fits in, here’s what it looks like:

I’m reading an e-book, an online article or blog, or tweets; I don’t use Readwise for scholarly articles which I have as PDFs. I make highlights related to a current interest of mine, either because I’m reading for that interest or because I notice something that relates even when reading for fun.

When reviewing highlights, I’ll add topic tags and notes as appropriate. After making sure all the metadata and formatting is cleaned up (seriously, remove the markdown footnotes if you highlight Wikipedia articles), I sync those highlights in Logseq to create pages. The pages generated by Readwise now become one part of an eventual reference (or literature) note.

Screen Shot 2022-06-26 at 3.29.36 PM.png

I have some fleeting notes, and I decide to make a Zettel (or main note) out of one. Because what I want to say is usually in response to something else, I like to make a reference note for that something else. If the source is not already in my Zotero library, I add it. Then, I make a page for that reference in Logseq via the Zotero integration. If I also have Readwise highlights for that reference, I put a page reference in the reference note to the highlights page.

Screen Shot 2022-06-26 at 3.13.58 PM.png

Now, when I write my Zettel, I can cite my source by linking to my reference note.

Screen Shot 2022-06-26 at 3.24.06 PM.png

I don’t link to the Readwise highlights page, but because that page is linked in my reference note, a link is created between it and my main note I’ve just written. I can also do block references with specific highlights I want to use as quotations. However, I don’t do this because I publish my Zettelkasten online, and it can only handle block references to other pages I’ve published; I don’t put my Readwise highlights or reference notes online. There is a Logseq plugin which allows you to swap a block reference and a block, but when I’ve tried it in this workflow, the block id gets included in the Hugo-compatible Markdown.

And honestly, that’s pretty much the main workflow!

Other uses§

I do not makes notes of everything I read, watch, or listen to just for the sake of making notes. But a nice thing about having my captured highlights in Logseq is seeing how clusters form, generatively, without me necessarily having done anything.

Let me explain.

Like how the Zotero integration brings in tags, so too does the Readwise integration. This includes the hashtags in tweets, in addition to whatever tags I’ve added to a highlight. The giant cluster at the top of my graph isn’t any sort of "main note" cluster at all: it’s a cluster of Readwise highlights linked to the page "art." It’s so big because a lot of tweets I send to Readwise that have art in them have the hashtag "art."

Sometimes, I will review highlights to see what tags or notes I might add. I use the Logseq Random Note plugin for that, and because so many of my Logseq pages are actually from Readwise, a lot of the notes I see when using the Random Note plugin are Readwise highlights.

I don’t tag every note that comes up. Just like when I’m reading, I only try to add tags or notes that are relevant to a current interest of mine. I don’t need to tag [this incredible tweet of David Duchovny on Celebrity Jeopardy](https://twitter.com/yacobg42/status/1325500299440754690 ?s=20&t=gT9ckEjkcf-jc8eLEjqpUg) with "frogs" or "X-Files." But if I see something that is related to a topic, I’ll tag it or add a related existing page.

Screen Shot 2022-06-26 at 3.58.32 PM.png

I’m beyond excited to see where the Logseq Readwise plugin goes. I love it so much as is, and it’s only just starting. I think Logseq and other tools which include block references are a perfect match for Readwise. It’s so nice to be able to link to or embed individual highlights without those highlights having to be on their own pages out of context.

I am also not someone who thinks we need to do something with every bit of information we interact with; I get exhausted just thinking about the people who write huge book summary reading notes for every single thing they read. But having Readwise highlights in Logseq allows me to add notes, tags, and links to highlights as needed. Plus, Logseq’s "Unlinked References" section and the Random Note plugin can create moments of serendipitous discovery.

And that’s how note-taking and personal information management should be: serendipitous and fun.

Shameless plug time§

To whoever reads this: I would love to hear about your workflows, especially if you use Zotero.

If you’re curious about using Zotero in a workflow which includes the Readwise integration, I offer coaching, mentoring, and consultation for Zotero in personal information management. Don’t hesitate to reach out to me: https://linktr.ee/jlcolbert
🕒 Last updated 2022-07-16 23:29:54
📚 Agora node [[icanhazzettelkasten]] (pulled by the Agora)
📜 File ICanHazZettelkasten.md by @agora@botsin.space ☆ 📎
🕒 Last updated 2022-12-05 23:41:24
📚 Agora node [[inter brain zettelkasten]] (pulled by the Agora)
📜 File inter-brain-zettelkasten.md by @neil ☆ 📎 ️🔗 ✍️

Inter-brain zettelkasten§

13/ PART II. Twitter is not only a notes-app with a dopamine slot-machine feature; it is also an inter-brain zettelkasten.

– https://twitter.com/kcorazo/status/1252669453961031680

See [[Threaded Twitter]].

The [[IndieWeb]] is my preference.
🕒 Last updated 2021-12-23 18:13:31
📚 Agora node [[organize your knowledge with zettelkasten]] (pulled by the Agora)
📜 File Organize Your Knowledge with Zettelkasten.md by @binnyva ☆ 📎

Organize Your Knowledge with Zettelkasten§

Organize Your Knowledge with Zettelkasten§

Source§

Organize Your Knowledge with Zettelkasten

The process§

  1. When you come across an idea, white it down. This is your inbox. Write it in your own words rather than copy/paste. Site your source in these notes. In my case, its in a text file.
  2. At the end of the day, import than into your Knowledge Tool(Eg. Foam, Roam Research, Notion, etc.)
    1. When doing this, link to other existing notes.
    2. Keep it as small as possible.
    3. You can give the note an id like the date/time it was created(This will let you change file name without losing the links.)
    4. Add tags to the note

Tags§

#knowledge-management #ksm #life-management #literature-notes #notes #video #zettelkasten
🕒 Last updated 2021-03-28 22:31:16
📚 Agora node [[permanent notes in zettelkasten]] (pulled by the Agora)
📜 File Permanent Notes in Zettelkasten.md by @binnyva ☆ 📎

Permanent Notes in Zettelkasten§

Keep this in mind when creating a new permanent/concept note in Zettelkasten…

  • Does the new information contradict, correct, support or add to your existing content?
  • Can you combine it with existing content to create something new?
  • What questions are trigged?

Some rules for permanent notes…

  • Write one idea per note.
  • Write as if you are writing for someone else - use full sentences, show sources.
  • Be precise, clear and brief
  • Should be understood even if you don’t know the context it was taken from.

Tags§

#permanent-notes #zettelkasten
🕒 Last updated 2021-03-28 22:31:16
📚 Agora node [[reframing and simplifying the idea of how to keep a zettelkasten]] (pulled by the Agora)
📜 File reframing-and-simplifying-the-idea-of-how-to-keep-a-zettelkasten.md by @neil ☆ 📎 ️🔗 ✍️

Reframing and simplifying the idea of how to keep a Zettelkasten§

An : [[article]]

Written by : [[Chris Aldrich]]

Found at : https://boffosocko.com/2022/06/10/reframing-and-simplifying-the-idea-of-how-to-keep-a-zettelkasten/

[[Commonplace books]], [[zettelkasten]].

Really nice summary of the minimum of what you need to do to keep a ‘zettelkasten’, cutting through a lot of the complexity that has appeared around this.

  • start with a commonplace book
  • add a way to find things again (could be an index, could be search)
  • keep reference / bibliography notes
  • summarise and rewrite ideas in your own words
  • link individual notes together
  • answer a question by finding your notes on the topic, following the links you’ve made, and pulling together your summaries

Similar in spirit to e.g. [[Collector to Creator]]. But I like that Chris frames collector as a perfectly valid and minimal friction starting point.

collect interesting passages, quotes, and ideas as you read.

No stress to create just yet.
🕒 Last updated 2024-03-18 12:55:07
📚 Agora node [[thinking in zettelkasten]] (pulled by the Agora)
📜 File Thinking in Zettelkasten.md by @binnyva ☆ 📎

Thinking in Zettelkasten§

The main work of understanding happens when we think and make connections. The [[Zettelkasten]] work flow makes thinking a concrete step - when you convert your fleeting notes to permanent notes. This also makes us think how this information is connected to our previous ideas - this makes connections between ideas(new ideas emerge). And also, will let us remember better.

Tags§

#zettelkasten #permanent-notes #learning
🕒 Last updated 2021-03-28 22:31:16
📚 Agora node [[twitter as zettelkasten]] (pulled by the Agora)
📜 File twitter-as-zettelkasten.md by @patterning ☆ 📎

eh
🕒 Last updated 2026-10-29 04:50:48
📜 File stoa-test-2/twitter-as-zettelkasten.md by @agora ☆ 📎

eh
🕒 Last updated 2026-05-25 20:37:19
📜 File stoa-test/twitter-as-zettelkasten.md by @agora ☆ 📎

eh
🕒 Last updated 2026-05-25 19:05:38
📜 File twitter-as-zettelkasten.md by @anonymous@doc.anagora.org ☆ 📎 ✍️

eh
🕒 Last updated 2026-10-29 04:50:50
📜 File Twitter as Zettelkasten.md by @an_agora@twitter.com ☆ 📎
🕒 Last updated 2022-01-27 05:38:44
📜 File twitter as Zettelkasten.md by @an_agora@twitter.com ☆ 📎
🕒 Last updated 2022-05-26 14:23:25
📜 File twitter as zettelkasten.md by @an_agora@twitter.com ☆ 📎
🕒 Last updated 2022-01-27 08:10:21