It would be beneficial to post directly to Discord (or StackOverflow, etc) directly from Dendron. Where each "post" turned into a thread synced between your local machine and the Discord server. Same thing with email. Writing posts, emails and responses first in Dendron and keeping them in sync would be a huge foot forward in PKM.

@User > It would be beneficial to post directly to Discord (or StackOverflow, etc) directly from Dendron. Where each "post" turned into a thread synced between your local machine and the Discord server. This is how I use Dendron actually - I will author my messages in an interaction note (eg.

daily.journal.2022.02.12.m.directly-posting-with-dendron

), write out my comments, and then copy and paste. This way, instead of losing my correspondence in Discord, I have a historical copy of my text locally (plus its much nicer to edit using vim/vscode then the discord chat). This is also exactly the workflow that podsv2 (https://wiki.dendron.so/notes/H9HVUUG1Z9ws2ngofKyWt.html) wants to enable - author something as a note and then publish or sync to any other destination. @User > My style of computing is quite different from yours, I think - I tend to prefer lots of small, specialized tools integrated together over monolithic programs. I hope Dendron will continue to be useful for both of those disparate kinds of workflows! I also like specialized tools. This is a key design principle that makes Dendron different from Notion - Notion wants to be the one place for all your use cases. Dendron wants to help you structure and organize but then make use of your information where its the most useful (aka sync with the best tool for the job)

Thank you for Pods explainer! This looks really cool. I'm working on responding with md created in Dendron but, hitting a snag.

Hey @User, which export pod did you use?

Hi @User . I figured it out! The PodV2 Quickstart instructions are a little misaligned with the current user experience (no biggie).

haha, pull request would be awesome! plus you'll earn the

taxonomist

badge if you do 🙂 https://wiki.dendron.so/notes/42917c62-a456-44b8-af22-d0360abcc489.html

Yeah, I still have a problem with integrating cloned repos into my Dendron "world". - I'm finally getting away from the "folder mindset" (

C:\Users\me\Documents\<project-ghrepo-etc>

) - Yet, I have to clone this repo somewhere (or part of it with a sparse checkout) - This is a gap in my (and I think a lot of others) mental map of how best to work with "projects" alongside Dendron - I don't yet have all the kinks worked out!

Hmm, to make sure I understand the context, you asking about managing docs for different git projects (eg. code) with Dendron? The way I currently manage it is using a global

kevin-private

vault. Every project that I create, I create a corresponding entry in my personal [[Project|proj]] hierarchy

I'm leaning toward: - From within my (single) Dendron vault:

git clone https://github.com/dendronhq/dendron-site.git --no-checkout --depth 1

-

cd .\dendron-site\

-

git sparse-checkout init

-

git sparse-checkout set vault/dendron.topic.pod-v2.quickstart.md

-

git checkout

-

cd vault

- Make changes to the single markdown file in question - Etc

ah, i see. you should be able to add the dendron docs directly to your workspace.

Vault Add

, select

remote

, select

dendron

Yep. That's basically what I did in the above commands except its just the single doc in question. Not the whole site/wiki.

got it. curious for during the sparse checkout. is it a concern of pulling in too many extra files?

Yes. It feels clean to see only the file that I'm working on. Reduced clutter.

nice! for myself, I never use the tree view but navigate solely on lookup and its useful to have all my notes with me at all times. this might be because rely on lookup/schemas for everything so no longer use file explorer or tree view to look at notes

I'm into that! I'll say that there is something to having a visual representation vs. a complete mental map. Or maybe i'm just getting old! 😂

i'm in agreement about the value of having a visual component. I think local graphs are actually pretty useful to spot outliers or things that are not filed away properly

Like right now, I hit a conflict with `...I never use the tree view but navigate solely on lookup...`: - I have a local directory in

C:\Users\me\Documents\<projectX>

that is an Azure Function project (Python and corresponding files) - I wrote the Python as opposed to wrote about it in markdown (Dendron) - How do I KEEP Dendron in context (so I can add to my kb in any one of its topics; Azure Functions, Python, git, etc) AND open the directory to work on the Python script/corresponding files? - Because right now, I can't Lookup the Python script. Its not in my Dendron Vault / VS Code Workspace. - Do I have to create a stub-out in Dendron for each "project" then link the stub-out doc to the directory on my local machine? OR - Do I add the project directory to my vault? Or something else?

> - Do I add the project directory to my vault? You would want to make your project directory into a [native workspace](https://wiki.dendron.so/notes/lamzybrD6SgQlJ9BpwkQk/), and add the vault you want to work along with the code there.

Hm. I'm not sure thats what I want. - I have 1 Dendron vault to house all personal knowledge - I want to keep this vault in context while I work on other projects inside VS Code - This is so I can add to my vaults topics (Azure, Python, git, how-to's, etc.) while still developing and testing code

To have the distinction of context and have it alongside corresponding projects, your vault may have to be split up to multiple vaults that only house specific topics (and have them remotely available so that it could be pulled in elsewhere). Otherwise I can see how this could work with one vault and using the sparse checkout you have mentioned before, but it isn't something Dendron natively support right now.

What happens if I just move the project directory into my single vault?

you can do the same in native workspaces.

And have just a single Dendron vault for my entire life?

So, if I'm understanding correctly, you want to, say, have your entire python project in a vault?

Yes. I want every project to be accessible while within my Dendron knowledge base.

The best practice that we recommend is have relevant vaults in your project.

I do not want this...

You could certainly do it, I don't see anything that would break this. It's not how I would prefer it, but I don't see any issues if you prefer it that way.

Thank you both for the insights. *I guess the part I'm struggling with is: * - I need one knowledge base (1 Dendron vault) for all the "things" in my life - Recipes, To-Do's, research, Discord threads, emails, StackOverflow posts, diagrams, daily journals, etc. - I need this to be right along side of me as I use VS Code for development (terminal, writing code, etc.) With one-vault-per-project or something similar, I can see myself getting frustrated looking for my content.

Nice! Please do report back if you run into some issues. It would be a great case study for us. I can definitely see why some would want to have everything in one monolithic workspace. We'll direct people to you as a pioneer of this use case if it gets brought up 😄

Thanks for being patient with me 🙂

Woah, this is a whole different way to organize your knowledge base 🤯.. Ability to use the power of dendron and lookups always at your fingertips. Knowledge consolidated and contextual. I can see how vscode workspaces can get in the way. Maybe multi vault with a main vault and perhaps a lot of project specific mini vaults could work? Probably not necessary to make a vault for every project.. 🤔 or would that be too bad for performance and integration?