@here One of the questions I get asked a lot, especially from new users, is how people are using Dendron. We're putting together a page of use cases to showcase both common and unorthodox uses of Dendron. If you have a minute, would appreciate a few lines about how your using Dendron in a reply. Public github repo or page link a plus 🙏

I didn't make the time yet to set up my own proper Dendron repo, but I read the documentation and used that as a sort of "literature study" on which notetaking methods and strategies are being used by people. Have too many priorities right now to dive deep into experimentation mode, but for now I do enjoy the process of preparing my transition to a better system. So I haven't yet gotten to the standard use cases of Dendron, but instead used your wiki as a really cool resource for learning more about PKM systems.

Thanks @User - through your readings/learnings, if you come across concepts and topics that should be consolidated here - feel free to add topics (even if it's just stub articles): https://pkm.dendron.so/. I'm hoping to build this out into it's own resource to help more people learn about PKM systems.

Cool, will keep that in mind!

I use Dendron to help classify notes for work and also write documentation for work. I use Dendron primarily off-line and so do not have a public git repository since the materials contain information about my clients. I create and keep track of clients, systems, project documents, system documentation, and project or system issues. I use the Mermaid and PlantUML to diagram system architectures, workflows, state processes, etc.. I have also dabbled with writing agreements and contract templates using field replacements for export to Word or PDF files using Pandoc, but that hasn't quite worked out as intended because Pandoc; works fine using PDF export using puppeteer. I do leverage Pandoc export for other documentation however, and that works phenomenally.

I mostly use it as a replacement for OneNote in making/organizing a ton of disparate notes/thoughts. Every semi-lenghty blob of text I write goes in there somewhere. I use it primarly offline, as I got spoilery things of my shadowrun campaign inside 👀 . Basically: I use it as a non-linear notebook of sorts.

@User Just wondering, would you say then that the combo of hierarchical classification or fulltext search has been useful in finding what you need when you need it?

I usually find it using plain old memory, but I greatly enjoy the hiearchical notekeeping as well as the quick search of VSCode x)

It certainly is easier to find (and organize) my stuff than in OneNote.

Plus, the ability to somewhat easily refactor stuff and text versioning is really nice to have.

Oh and snippets. Thank god for snippets. I've got one for a nicely formatted markdown character sheet and it make stuff so much easier

cant public, but to turn my obsidian vault into project management wiki 🙂

I've been thinking of creating some scripts that continuously convert and maintain Dendron vault version of: - Linode docs (mix of CC-BY-4.0 and CC-BY-ND-4.0 docs), especially the configuration management guides that I find relevant to particular tech I work on that isn't Linode-specific: https://github.com/linode/docs - There is also OWASP: OWASP has markdown/Jekyll docs spanning across multiple repositories. I can imagine a GitHub Action that is scanning them for changes, and updating a primary

dendron-owasp-vault

based on changes. It looks like I'd have to use some magic to strip out Liquid templating where I can, and update internal links to be Dendron links. Their content is CC-BY-SA-4.0, also. I have been monkeying around with one of the OWASP repos to get an idea of what could automatically run against them. I don't know TypeScript/Javascript, so I haven't gone the route of trying to make a custom pod. Instead, I've been using bash shell and Python, since I'm more familiar in that world. I haven't had time to really dedicate toward it, but I think these would be beneficial vaults, similar to the approach of Dendron-vaulting AWS content from multiple sources in dendron-aws-vault

that would be awesome. we just added the [tldr](https://github.com/tldr-pages/tldr) docs to the remote vault presets [[dendron.topic.multi-vault#preset-remote-vaults]] https://wiki.dendron.so/notes/9bc92432-a24c-492b-b831-4d5378c1692b.html#enhancements the plan is to keep it up2date using github actions. you can see the github repo here: https://github.com/kevinslin/seed-tldr the cool thing here is that it required basically no custom code, just the markdown pod and a script to clone the docs. you can see the hosted version at https://tldr.dendron.so the cool part about this is that clicking

edit on github

on any of these pages will take you to the official tldr page on github

let me know if you want pointers for setting up the linode docs. would be happy to help out 🙂

Do you work for linode or just host projects on their platform? Do you mind if I DM you?

No, I don't work for Linode, but they have docs that I'm interested in using, like the ones here: - https://www.linode.com/docs/guides/applications/configuration-management/ They've just created and manage a large library of guides and docs, Linode-related and otherwise, that seem really useful, especially being under a creative commons license allowing for the docs to be ported

I work on stuff coming out of Salt Project (previously SaltStack) - we were acquired last year by VMware: https://github.com/saltstack/salt/

Sorry if I came off nosy, just curious because I just got started bug bounty hunting on their platform 🙃

As a wiki tracking topics Ive studied, with review questions in folddown. I create inpromptu stubs of cladograms with dendron's hierarchy as I go though materials that alert me to gaps in my knowledge, spaces that I would fill in later as I cover more in the subject. I make review sheets by referencing notes. And as I learn more about a topic or encounter more information in practice exams, I add in the information I learn into each topic hierarchy

2. As medical script template. Inspired by Epic EMR's dotphrases automating tedious medical notes. I'm also using it as an applicaiton and study lists database to organize my medical thinking and decisionmaking process.

3. To track my conversations with multiple people over multiple topics over time. Some people I talk to may not be familiar with some topics, and I may not be familiar with some concepts people talk to me about. We sometimes understand words that are said but don't understand the hermeneutics and the layers of knowledge and references behind the ideas and phrases. I note these in Dendron and can come back to conversations with people after I understand topics better.

your setup for folding and review spreadsheet kinda reminds me of this: I'd applied this in Notion as well in the past, but won't it be more efficient to use SRS like Anki (using vsc anki extension) Thinking about apply this as well, an advantage I see for using this in Dendron is you can get a great hard copy (without anki syntax) when you want to

Markdown pod is awesome!

One of the ways I am using Dendron is to learn more about how different historical figures, movements, concepts etc. relate to each other. It's cool to open up a time period from the hierarchy and see patterns emerge.

Hmm.. Still playing around with Dendron. This page is not complete, but just a sample doc I am testing with: https://notes.jthan.io/notes/9ae3165f-7803-4a7f-9315-526174bd6c21.html. One thing I notice is that literal (\`\`\`) blocks only wrap the text with a grey background, but I think it should just be the whole section. Compare to the configuration section of the README here: https://github.com/jrdemasi/gh_authkey_checker

Not even a dendron thing, just a theming thing when publishing.

It looks like it's using prism, at least... I use prism on my blog as well, but it doesn't behave the same way. wondering if I'm just doing it wrong 😆

I also realized though that it shows "correctly" or as I'd expect in the markdown preview in vscode. So I feel the published version should match.

Huh, okay, so it fixes it (kind of) if I add a language for syntax hilighting, but I still think the default should behave differently. I know that's an opinion, and sorry for rambling.