I’m using the Zettlekasten method in Obsidian for ideas/academia information via atomic notes. I haven’t written any documents/articles/books based on any of my ZK notes. I plan on using KOHighlights or similar highlighting app (for ebooks) and Zotero (for articles and webpages) to import “Literature/Content” highlights into MD notes. I will then write a new note/rewrite the “Literature/Content” note summarizing the highlights in my own words.
I’m using a tag centered approach for bookmark management in Obsidian. So far I’ve been using the bookmark manager to collect links to items I want to buy or forum posts/configuration instructions on different interests (ie: as shown below).
My current hangup is on technical information. I have an answer for the end of the process: Documentation
Whether it is a Document (or note) with all the specific steps and details to auto mount my SMB share via fstab on my Debian with Gnome laptop and customize the user-dirs.conf so my file manager has SMB share based links for Documents, Pictures, etc.
It’s the collecting and retrieving setup I’m having trouble with. I was wondering what others are doing regarding collecting/storing and retrieving technical information (IE code snippets, configuration scripts/information, how-tos, etc)?
Like when you find a forum post on how to customize your OS’s file manager or setup an SMB share, specific instructions on an application wiki that answers what you are trying to do, or a blog post that answers a configuration/script/etc question how do you save that information?
- Do you just save a link to it and hope it doesn’t go away?
- Do you print/save the page as a PDF and keep it local as a reference?
- Do you use a Webclipper plugin/app to only highlight the answer in question and a link back to the source via a note?
- Do you use the Zettlekasten method to make short atomic notes for the “answers” as well?
- Do you use something similar to a bookmark manager with tags to organize the information?
Thank you in advance for your time, assistance, and any feedback!
I like for my system to be flexible. So, while I use a more Zettlekasten approach for my general ideas or notes, I have a folder (or tag, if you wish) for snippets and how-to I may need in my technical work.
Usually I just clip or rewrite the answer in a note and then I expand it in case I find not-documented error or problem specific to my environment. So, for instance, I have a “How to install MediaWiki on Docker” note that started by web-clipping a post on a forum. Then I integrated it while trying to actually install MediaWiki on my system (e.g., it happens that I have to update outdated commands; or add steps that the original author takes for granted). Finally, I store the “source” at the end as a link. Just in case.
I do not try to force the Zettlekasten approach on those notes. I prefer them to solve a specific problem. But, of course, I can reference them in a zettle note, if it happens to make sense.
1 Like
Thank you very much your reply and thoughts! I’ve been trying to find a balance between retrievability and information hoarding. I also noticed that I was starting to run into some friction with all of my collecting and organizing when it came to actually using the information. There is definitely less effort in summarizing the information, including the needed steps/details, and linking to related sites in one effort vs maintaining a collection of related information that was used in addition to the aforementioned effort.
Your approach also provides some guardrails to avoid letting things go unfinished for too long or trying to do too many efforts at once. I tend to get distracted easily lol.
Thank you again!
This sounds like an issue I encountered before.
I’ve been using the ZK process to manage my note taking system, but some pain points remained unresolved:
- Sometimes I need to save the original text of some literature, such as web page archives, personal output article archives, and templates, which have no place in the ZK system.
- Daily goals and some structured materials (like collections of test questions) have no place to be stored.
- Sometimes engineering like files, such as code snippets, color matching references, and plugins, have nowhere to be placed.
Initially, I added a major category in the ZK system: 专案（I’m not sure how to accurately translate this word
,like “a special project case”）
Is look like:
- Fleeting
- Literatur
- Permanent
- 专案 (special project case)
But it’s still a bit strange to use, it’s like a universal pocket.
Recently, I came across PARA integrated vault ，which sparked my inspiration. PARA can be used by me for goal management and archiving.
This concept can perfectly solve my question: PARA-Resources stores original archivals, like book,literature, web archives, originals from other software sync, and code snippets. PARA-Area has self output content. PARA-Project handles project progress management.
New category look like:
- Fleeting
- Literatur
- Permanent
- PARA-Projects
- PARA-Areas
- PARA-Resources
- PARA-Archives
This is my share ,maybe can help you:
Share on Applying PARA in Zettelkasten System - Share & showcase - Obsidian Forum
1 Like
Hello and thank you very much for your reply and feedback!
In part from your linked post:
PARA3-Resources (resources, literature, interest points, tool tutorials, configuration files)
....
Loose article category (web page archives)
Sync collection category (sync WeChat reading, official accounts, etc.)
Skill areas
Programming (Geektime courses, programming configurations, code snippets, operations related)
Tools (software configurations, instructions, sync templates)
Are you capturing web pages or instructions in their entirety and keeping a local copy?
As an example, I have a Technical note that I created called “Auto-Mount SMB Share Debian” and inside I have all the steps and code snippets needed to do so. At the bottom of the note I have a “Reference” section where I have a list of links that I used to create the steps and code snippets in my note. The links are as follows:
Would you just link to the sources like above or would you capture the content (PDF, HTML or MD Export) and retain an offline/local copy and maintain a content library of sorts?
Thank you again!
The core of my workflow is PARA focuses on action, and ZK focuses on knowledge accumulation. PARA is as lightweight as possible in this workflow.
In my app, Resources files store originals, usually in MD format.
-
I convert web pages to MD (e.g., using Obsidian Web Clipper).
-
MD formats from other reading apps via sync (e.g., from Weread / Kindle).
-
I extract text from PDFs and save as MD (usually copying text during in depth reading).
However, there are exceptions. For some non in depth reading materials like literatur and books, I plan to link to PDFs in Zotero via MD links, preventing rapid note system inflate.
To your question about whether links are all archived, here’s my take: Both PARA and ZK share a common approach — progressive filtering/knowledge extraction/inductive thinking.
For me, I only archive web pages when they’re crucial and I worry about future access. If I’ve absorbed the core content and just need to cite the source, I won’t archive. Still, archiving doesn’t mean it’s static. Knowledge flows, and I might clean up archives. So, I usually archive only the most essential content, linking most materials directly.
1 Like
