@User specific is great. for R files (or more broadly, anything that is not markdown), Dendron's convention is to keep them under an

assets

folder in your vault. for example, images are saved under

assets/images/

and referenced as

/assets/images/*

inside your notes. you could do the same today with scripts (eg.

assets/scripts/

or assets/r/`), navigate to them via regular vscode (cmd|ctrl p), and then include them as code chunks in your markdown. the preview accepts running code chunks. you can see the instructions here: https://shd101wyy.github.io/markdown-preview-enhanced/#/code-chunk vscode is also adding native support for notebooks so as that support becomes more mature, we'll probably look into making this process less kludgy. let me know if this works for your current use case or if there's something more you want to see 🙂