# [[A System for Writing - reference]] ![[A System for Writing - lit.svg]] Zettelkasten steps 1. Capture ideas in the form of fleeting and/or reference notes. 2. Create main notes. 3. Establish connections between main notes. 4. Create hub notes, structure notes, and indexes. (high-level views) 5. Create something. Terminology - "reference notes" instead of literature notes to be more applicable to non-literary content sources - "main notes" instead of "permanent notes" Fleeting notes should be staged in an inbox for processing later (recommended weekly). Any notes that can't be processed should be moved to a "Sleeping" folder. ![[system-for-writing-diagram.png]] This diagram is similar to [[Getting Things Done]]'s GTD flowchart. > Not all fleeting notes need be transformed into main notes. For best results, practice [[Non-attachment]] when it comes to fleeting notes. - ? How do you determine what's "zettel-worthy"? - Reference notes have page numbers, a description of the insight, and then a keyword/phrase for the insight ![[system-for-writing-reference-notes-workflow.png]] - ? What do you think of automating the process of creating reference notes with tools like [[Readwise]]? - ? Why are page numbers so important to keep track of? Things to keep in mind while consuming content - Consume with a question/problem in mind - Capture ideas you disagree with - Capture what you think about what the author thinks - Capture someone else's interpretation (if it captures your attention) - Don't forget fiction - Go wild with your captures: capture everything that excites you even if you don't have a reason for it A main note should have at least: - A single idea - A link to another idea stored in your ZK Optionally: - title - quote/reference to where the idea comes from - record pointing to where and how the idea has been used in your writing - unique ID ([[Folgezettel]]) - ! Create main notes from your own work - Key difference between Bob's system and [[Niklas Luhmann]]'s: Luhman created and developed ideas "in light of" what he already had in his ZK. Bob prefers to make notes "in spite of" what's already in the ZK. But he acknowledges that either is fine. - ? No revision of notes?! Luhman and Bob don't revise notes when they learn new information that contradicts them. Instead, they create a new note with the counter-argument and link it to the first one. - ? How do you know when a main note is "main enough"? "Atomic enough"? - Bob says this is personal and that's okay. Connecting ideas - ? How do you look through your notes to find a concept that is related? How do you hold the contents of your vault in your mind enough to make intuitive connections? - Add context to connections. How are they linked? Explain your thought process like you won't remember why you linked them later (you won't). - Bob and I share a love for exploring how seemingly contradictory or unrelated ideas from different fields intersect - Fear of getting lost: embrace the anarchy of ideas and delight in getting lost - Using folgezettel - ? Why a separate unique ID? Isn't a unique title enough? ([[Folgezettel]]) - It forces you to consider your notes spatially. - But isn't this just another extension of the folders vs. links/tags debate? - No - your notes can still be utilized in other contexts. - ? Are links and backlinks enough as folgezettel? - Folgezettel is *not* an outline. It's not organized by semantic logic. - Folgezettel is *not* a hierarchy. - Folgezettel show chronology. - ? What about using dates instead of numbers? [[Anarchy]] of ideas: ideas can spring from chaos Hub notes - Built around clusters of ideas - Identifies a topic and lists trains of thoughts springing from that topic Structure notes - Notes for developing clustered ideas further, not just a place to store references to them - They're structural outlines like for a book or article Keyword index - List of keywords and then notes where they're found - ? Can't you use backlinks for this? Ways to structure a zettelkasten (so you don't get lost) - Folgezettel - Hub notes - Structure notes - Keyword Index Figuring out what to write/create content about - Folgezettel (alphanumeric IDs) identify long trains of thought - Look at your reference notes - they show you what's caught your attention - Use structure notes as a starting point for your writing - Let main notes help you with composition - When a structure note becomes really long, turn it into a longer form of work *and* also make sure you break it up into smaller chunks to feed back into your ZK - ! Using filenames that are summaries of the contents of the note (rather than just a keyword) helps you look quickly through your notes - ! Avoid copying notes into manuscripts. Your ZK is a terrible writer because those notes weren't written with the same context in mind. Instead, rewrite the ideas into something coherent. Pitfalls in writing with a ZK - Writing can get repetitive, using the same citations and turns of phrases - It can feel like you're trying to cram in too many ideas - It can feel chaotic and disordered - Ideas may seem to be lacking context Creating content - Turn main notes into "short-short content" - Gauge reactions and responses and iterate on the original note (or create a new main note) - Blog posts: rewrite main notes + related notes - Longer-form writing - Let yourself ebb and flow from top-down to bottom-up. This is natural. - Pick a topic (maybe pick a structure note) and bring in multiple main notes/ideas. Rewrite everything so they fit. - Books: Start with abundance Managing writing projects - Keep a daily journal - [[Interstitial journaling]], developed by [[Tony Stubblebine]]: record your work, including unfinished work. Create a space for you to talk about multiple projects. - Keep a [[Creative Log]] (related: [[Devlog]]): track your progress and every working session on a project note. - Bob recommends one creative log per topic - How they work together: every day, read through the previous day's journal entry and then follow that to the creative logs mentioned. Creative logs are more specific. In the daily log it's enough to talk about which log you worked on generally and how it went. - ! Zettelkasten != Second Brain. Second Brains contain much more. ZKs only contain ideas. ## Related - [[A System for Writing]] (summary) - [[Zettelkasten]] %% # Excalidraw Data ## Text Elements ## Drawing ```json {"type":"excalidraw","version":2,"source":"https://github.com/zsviczian/obsidian-excalidraw-plugin/releases/tag/2.0.25","elements":[],"appState":{"theme":"dark","gridSize":null,"viewBackgroundColor":"#ffffff"}} ``` %%