One thing a I have some concerns about, is how can hierarchies will scale over time. I mean, with time you probably will have tons of notes with 80+ char file names. As always, thinking about future proofing our notes in case a tool like dendron stop its development (I hope not) I'm not sure how the names will play when you want to find something in particular (wo/ dendron of course). I think a good Idea could be decouple the hierarchy from the file name, having it in the frontmatter for example so the dendron capabilities could still be there, but with more readable names, separated with hyphens. e.g. You launch the lookup, and write: "*note.methods.hierarchy first note taking*". That will be populated into: hierarchy-first-note-taking.md and in the frontmatter: hierarchy: note.methods title: Hierarchy First Note Taking I'm not sure if this topic has been talked already

😳 D'oh! Clearly spent too long looking at code yesterday. Thank you.

We were talking about something similar over in the schemas channel - the ability to make notes members of secondary schemas in the frontmatter. Kevin mentioned he's working on some stuff in this direction. Whenever I work with a new tool I try and make sure I can get out of it and move to something else. The combination of yaml/markdown means that even if disaster strikes and Dendron didn't get developed any further, it's about as easy as possible for me to refactor everything into a format that would work for something else.

That's exactly my point, if you can decouple both things, you end up with a less "intrusive" workflow that can be refactored to other things in the future if needed

I would like to see how this topic is moving

If we turn the fm entry into an array like this we could plob notes easily into multiple hierarchys

yaml
title: "Hierarchy Fist Note Taking"
hierarchy:
 - note.methodes
 - pkm.methodes

Two things come to mind. 1. The fact that all the files are stored locally (in one folder) you can do whatever you like with them. It is very easy to manipulate the files. One can write a small script that will take a dendron folder, loop through all the files, and automatically create a nested folder structure (based on the hierarchy) and copy the files into their corresponding folder (with a short name) and write the original hierarchy in the front matter. 2. Once you start using Dendron you never look back. Saving all the files in one folder is incredibly liberating, fast and efficient. Try it for a few days and you will see. Getting your thoughts and information down into a hierarchy is so quick and easy. I am loving the experience. (I have only been using Dendron for a few days now. And it is a game changer for me. CTL + L is your friend.)

I didn't think about that, sounds amazing, and would make dendron hierarchies even more flexible. I think it also is more DRY compliant

I'm agree. I tested a lot of PKM apps, and dendron looks better for me for what you said. But if you think in for example non-technical people, the path of building such script won't be straight forward. In addition, maybe you don't want to migrate to another app, just for example just want to make some quick edits from your phone using Git Journal (or whatever). Looking at that file names from a phone doesn't look cool. And another possible thing is that for example you don't want to get rid off your hierarchy definition if you migrate, but you don't want to lose the one-folder approach either. Something like the hierarchy in the frontmatter would tackle all of this in one go

changes make sense. just a slight comment on switching to new style note references

just responded in the chat

thanks for the issue. also a heads up that dendron-11ty is now merged into dendron so all issues can go there now. i've been meaning to add a right hand toc but wanted to wait until it was requested 🙂

> 2. Once you start using Dendron you never look back. Saving all the files in one folder is incredibly liberating, fast and efficient. Try it for a few days and you will see. Getting your thoughts and information down into a hierarchy is so quick and easy. I am loving the experience. (I have only been using Dendron for a few days now. And it is a game changer for me. CTL + L is your friend.) that's a very kind praise 🙂 mind if I use it in our testimonials page? https://dendron.so/notes/b08155fe-c5c6-4d4c-a737-d500923f35ad.html

The docs mention that the dendron-cli doctor has different functionality from the doctor command built into the extension, but I'm not clear on what the difference is. The most salient thing to me as a user is that running the doctor command in the extension adds front matter to notes that don't have it. Could I expect the line

dendron-cli doctor --wsRoot . --enginePort

to do the same thing if run inside a dendron vault? Does the 🚧 emoji indicate the doctor command is deprecated? What are the risks involved with using it? I'm trying to figure out a terminal-only interface.

Hi Dendon Team! I wanted to follow up from an older question. Basically I have been working on a custom Dendron hosting setup which doesn't involve Github pages/AWS amplify etc. My requirement was to hide the generated dendron static website behind a company VPN (i.e not accessible publicly). The solution I have in mind is to connect the dendron git repository through a Jenkins pipeline to an S3 bucket that is configured for static site hosting. I can then set the S3 bucket policy with appropriate access permissions. So currently my build steps are 1) generate artifacts using command - npx dendron-cli buildSiteV2 --wsRoot . --stage dev --serve 2) copy the artifacts from ({workspaceRoot}/build/site) to the S3 bucket. This doesn't seem to work however. The landing page doesn't seem to render correctly (screenshot to follow this reply) and also none of the links/pages/notes work - since on clicking them it redirects to localhost:8080 rather than keep the baseUrl for the S3 bucket. Is there a way to fix this problem?

broken landing page

Hello! I just discovered Dendron and it's wonderful! I was wondering if anyone had tips/directions to workflows for using Dendron as an electronic lab notebook? I code in VSCode and was thinking perhaps referring to Git commits might be a way... any advice or tips would be greatly appreciated!

dendron when being built for dev renders urls to 8080. you want to set the stage to ‘prod’ and update the siteUrl pram in dendron.yml

2 questions. 1) what do i do with the githubCName param in dendron.yml. Is that relevant in my context? 2) Where are the artifacts generated if I pass

prod

in the npx command? Are they overwritten on same location as

dev

i.e. {workspaceRoot}/build/site

1) nothing. you don't need it if your not using github 2) artifacts are generated in

docs

but this is configurable. see https://dendron.so/notes/f2ed8639-a604-4a9d-b76c-41e205fb8713.html#siteurl

i don't do anything in this area but if you describe you use cases, might be able to help

> mind if I use it in our testimonials page? Sure

awesome, what should I put you under for role? format is

testimonial, - $name, $role

role: Co-Founder

What's the difference between:

dendron.dendron-markdown-notes

and

kortina.vscode-markdown-notes

? The first one does not exist in vscode marketplace (at least for me

Dendron-markdown-notes was a fork of vscode-markdown-notes that supports dendron specific features but it has been deprecated for a few releases now.

The functionality is now part of the main plugin

But in order to have backlinks, I need the

kortina

one. If I remove it there is no backlinks. I guess is something pending to add in the core plugin right?

Backlinks work without the kortina one for me do you have an example where the backlink does not work?

As you can see there is not a backlink pane if I disable the kortina plugin