The "Dendrons Config" page (I think it should be Dendron's Config ?) in the wiki is a bit difficult to read. It's difficult to figure out the hierarchy that a property belongs to and also some properties are getting capitalized in a confusing way, because they are defined as markdown headers. Personally an html render of the json schema for it would be much easier to understand. But it would be difficult to integrate with the rest of the wiki. So it would be nice if the existing page would be made a bit more consistent and clean. Also if anyone could point me to the json schema file in github that I heard exists for validating the dendron.yaml, I would be thankful

You just need to install the RedHat YAML extension to get the validation, after that you should see warnings and autocomplete when editing

dendron.yaml

@hikchoi is working on simplifying the configuration, and I think we'll be updating the docs with that too. Please feel free to leave any feedback with that here: https://github.com/dendronhq/dendron/discussions/1260

Thanks. The yaml plugin validates the config now 👍. Also I was able to find the "dendron-yml.validator.json" in the repo, so I can render it with some 3rd party jsonschema viewer

we will be doing 2️⃣ [Renaming scratch notes should update links with exact alias](https://github.com/dendronhq/dendron/issues/1502) as last weeks crop. thanks for voting!

Yes, in preview of I have a list. List item 2. in the markdown is rendered as 1. in the preview. The list has nested subitems but numbers are on the first level. Text in preview should never differ from the text in the file.

I just realized what it is about the

.

hierarchy that is gelling so well with me: the hierarchy is part of the note name, but it doesn't display when rendering it. This is useful when you have two things with the same name, but different meanings. E.g. commands in CQRS vs. commands in CQS, a team name vs. a product name, or your body weight vs. font weight. With a different system, you have to make those distinctions some other way and it doesn't seem to work out too well all the time: - In obsidian, for example, you can keep one big note with headings and reference them so you'd see "CQRS > Commands" or something, but updating the heading doesn't update the references so it ends up breaking. - Or you can put a note in a directory, but then you usually don't get the hierarchy to display so you'd just see "Commands" instead of know which kind of commands you're talking about. - Or you put the hierarchy in the note name and now you have these super long references that don't read quite right like, "This [[The Marketing Department's Wiki]] is a living document." vs. "This [[department.marketing.wiki]] is a living document." Anyway, I'm sure this is an epiphany others have made over time. I just had mine and wanted to share it.

Also, I wasn't really sure where to put this. There's no real "general discussion" channel, and all the others seem pretty focused on something.

thanks for the feedback. there's a lot of power from having hierarchy be just the filename. kind of like with lisp where data is code and code is data. for general discussion, #717965437182410786 would be the channel 🙂

@User! It's CROP time 🙂 Please vote for your favored crop 👨‍🌾👩‍🌾 1. [Show Preview should not be available outside of a Dendron workspace #1545](https://github.com/dendronhq/dendron/issues/1545) 2. [Generate backlinks for links in frontmatter #1531](https://github.com/dendronhq/dendron/issues/1531) 3. [Enable setting Katex options from dendron #1535](https://github.com/dendronhq/dendron/issues/1535) 4. None of these (if there's an issue you'd like to add to rotation, please reply with a github issue) To vote, respond with a 1️⃣ 2️⃣ 3️⃣ or 4️⃣ to this message. voting closes Monday at noon Pacific Time

a bit confused about the search function on the wiki. i am trying to find the docs on mermaid and these results are a bit strage. am i missing something?

It looks to me like these files are supposed to have mermaid diagrams in them, but the diagram isn't rendering and search is finding the markup saying this is a mermaid diagram

I'll make a note to come back to the search for improvements, thanks for the feedback. In the meantime, here's the info on mermaid diagrams: https://wiki.dendron.so/notes/ba97866b-889f-4ac6-86e7-bb2d97f6e376/#diagrams

Looks like 1️⃣ [Show Preview should not be available outside of a Dendron workspace #1545](https://github.com/dendronhq/dendron/issues/1545) is our winner. We'll work on this item this week 🙂 Thank you everyone for participating in the CROP vote!

When dendron is updating its config in dendron.yml, it also rewrites and re-formats the workspace config file without making any changes apart from whitespace ones. Is this known/tracked? There was an issue a while ago about this problem: https://github.com/dendronhq/dendron/issues/572. Maybe it's a regression.

this is due to how migrations work. if we notice any pending migrations, we will update both the

dendron.yml

and the

dendron.code-workspace

. since the workspace file didn't have any changes, it just read and wrote the file, leaving the whitespace change

Fair enough. Just a little bit annoying that it keeps overwriting my formatting of the workspace config file, especially if no actual changes are made.

we can probably update this now since we're consolidating all configuration in

dendron.yml

. can you submit as an issue?

Done, thank you! https://github.com/dendronhq/dendron/issues/1595

Dendron: Move Header

is the most impactful and useful change to Dendron in the (albeit brief personal) history of time! This is a huge part of Dendron (and markdown as a whole) to be node based, which was a 1+ year long effort for the org-roam team from v1 to v2. It also bridges the gap between org-mode and Dendron by a mile, as it lays the groundwork for headings to be logical units of content that can be manipulated. Fantastic stuff! 🎉 🌱 🎉

credit to @hikchoi personally been using it a bunch for my own notes 🙂

dendron's install speed is noticeably faster, is that one of the improvements? 🤔

currently brewing some enhancement ideas for the Move Header command so stay tuned for more of that 🙂 I'll share it with the community once I spec it out a bit more

we’ve been working on the bundle size for the past few installs. so wouldn’t say it’s been cumulative efforts for past month 🙂

Where can I read more abt this?

Just talking out loud I wish the social media preview of these dendron web pages can be better

Thanks for the link

Again talking out loud, I wish there was a simple before and after diagram or image with arrows that show what these commands do. I think I will make a few PR to augment some of these commands with such images as I figure them out

they can - we just need to add image tags to them. here's an example of what it looks like with an image tag https://blog.dendron.so/notes/fDCVPEo3guCFWPdxokXHU/