https://www.dendron.so/ logo
Join Discord
Powered by
Eh... another topic... So, are you all storing no...
# questions
s
Eh... another topic... So, are you all storing non-markdown files in your Dendron vault? - Things like: python files (.py), sql files (.sql), PDF's, etc? - Or do you keep those in separate folders on your file system then link to them from Dendron as needed?
f
I think so far the recommended thing to so is keep all of those in your vault's 
assets
folder, if you want to combine them with your Dendron notes. You can then link to them from the most relevant markdown note (journal / project, whatever) or make a what's effectively "proxy" note.
Here's a little more on that ( https://docs.dendron.so/notes/WCZ1LzhM07Om3KFPERk6l/ ), plus the discussion happening about it on GitHub ( https://github.com/dendronhq/dendron/discussions/1975 )
Personally, I use the 
assets
approach, then usually have a Markdown file with my notes on the PDF or the context for that code.
s
Thank you for the insights. Would you then recommend to have subfolders in the assets folder to keep organized?
Something like 
vault/assets/project1
, 
vault/assets/project2
etc.
This is I continue to struggle with; I have to open Dendron then *open few single files and the terminal to "do work" (python, SQL, etc.). PROBLEM: - As soon as I close the single "work files" (.py, .sql, etc) the contextual relationship with my knowledge mgmt system and the actual work files is broken
f
I don't see any reason not to do that, but I've never tried it—hopefully other folks can chime in with what they do, too. My experience
My experience is mostly either reading pdfs (for research) or a few html and css files for various academic-related websites I work on… things like templates for html tables built to maximize screen reader accessibility, or that kind of thing. Not quite the same scenario as functional code I'd run in / work on in a terminal window.
5 Views
PreviousNext
Powered by