Small into docs updates

10 Notes/Short Introduction to Obsidian.md

@@ -1,5 +1,7 @@
 Here a short intro to [Obsidian](https://obsidian.md) and *Personal Knowledge Management Systems*. 
 
+We also have some video tutorials: see [[Using Codex Obsidian Vault Video Tutorials]].
+
 I currently, document some of the Codex/BitTorrent stuff in the vault you already can use to see how does it feel for you. The vault is available on GitHub: [https://github.com/codex-storage/bittorrent-codex-docs](https://github.com/codex-storage/bittorrent-codex-docs). You can just clone the rero, and open the cloned folder in Obsidian. That's it. This is you local copy - anything you do is only visible to you. GitHub is used for a more controlled syncing. Normally, when you work on your own content, you will put your vault on some shared network drive (end-to-end encrypted of course! :yum:  ), and then you can conveniently open it on any other device. Syncing is done by the network drive, Obsidian has nothing to do with it in this case. You content keeps the same structure (including folders) as you see it in your local (shared) folder - thus, everything is transparent and extremely portable. Myself, I have a paid subscription to Obsidian Sync service (not that I really need it, but I wanted to try it and to support the Obsidian team a bit). It costs me $96,00 per year:
 
 ![[Pasted image 20250513024925.png]]

10 Notes/Test Commenting.md

@@ -3,4 +3,4 @@
 
 Now, maybe the most important part is that Obsidian (as well as Logseq, and mentioned above Roam Research) are called Personal Knowledge Management systems. Those system can be used for project documentation and any other inventory, but their true power is in knowledge management. Sounds like nothing, but it was and still is new for me.
 
-I spent years "reinventing" my documentation systems and only after I discovered Obsidian I started to learn more about how to effectively record information in a way, that it is findable when needed, and fulfills quite a different purpose than many people expect when they think about documenting: a knowledge management system should allow you to be more productive in ***creating new ideas*** based on what you have learned before. A good intro is to look into the concept of [zettelkasten](https://en.wikipedia.org/wiki/Zettelkasten). You will find a lot of good free and paid materials on how to use tools like Obsidian or Logseq effectively. Of course, Obsidian is also very good on creating a traditional documentation without taking full advantage of linking and indexing, and it is still very convenient to use it as such - not everything is suitable for zettelkasten,  you just need to write longer manuals or tutorial or just keep you {++{"author":"mc2","time":1748264649}@@this is my suggestion++}home inventory.
+I spent years "reinventing" my documentation systems and only after I discovered Obsidian I started to learn more about how to effectively record information in a way, that it is findable when needed, and fulfills quite a different purpose than many people expect when they think about documenting: a knowledge management system should allow you to be more productive in ***creating new ideas*** based on what you have learned before. A good intro is to look into the concept of [zettelkasten](https://en.wikipedia.org/wiki/Zettelkasten). You will find a lot of good free and paid materials on how to use tools like Obsidian or Logseq effectively. Of course, Obsidian is also very good on creating a traditional documentation without taking full advantage of linking and indexing, and it is still very convenient to use it as such - not everything is suitable for zettelkasten,  you just need to write longer manuals or tutorial or just keep your home inventory.

10 Notes/Using Codex Obsidian Vault Video Tutorials.md

@@ -0,0 +1,3 @@
+I have recorded a couple of videos to guide you through some basics Obsidian stuff.
+
+They are all in one folder on my Proton Drive: https://drive.proton.me/urls/5J7C60803W#pSLc5V6l8maN