Then the weekly note (journals are organized as

daily.journal.yyyy.ww.dd

) template contains at a

![[${FNAME}.**#done]]

to generate a weekly summary for that week's days. Note I don't think the above pattern actually works or is buggy, but that's the idea.

task notes seem kind of interesting

will try to watch when I have time

should've made that a dendron task instead of spamming the channel 🤔

There is no indication that this config information is referring to namespaces in dendron.yml in the config documentation https://wiki.dendron.so/notes/j1120e2f53301nhdn1wkp05/

It appears that when you have an anchor like this:

^dllbuilddiff

in a note and reference it in the same note like this:

[[#^dllbuilddiff]]

then refactor the anchored line to a new note using move selection, the reference doesn't get updated. I'll try to remember to log a bug when I get a chance if no one else gets to it first.

It seems that the "+" button to create a stub note (https://wiki.dendron.so/notes/c6fd6bc4-7f75-4cbb-8f34-f7b99bfe2d50/#stubs) in the tree view doesn't work anymore--when clicked, I get this error:

I can repro. can you create an issue for this?

> - enhance(lookup): tab autocomplete in all lookup controls 🎆

> - fix(views): remove schema icon from tree view and published sidebar What's the reasoning for removing the icon?

I know I didn't like it because it makes the list have different indents... now I want to remove the + signs next to hierarchies... they already have the > next to them... I guess I should create a request

Yes, the uneven indents bugged me as well--I don't mind the icon gone. A while back I suggested a better placement for the icons (https://github.com/dendronhq/dendron/issues/767). It will still work for the "+" button:

a lot of folks brought up that it was bothering them when publishing - theres value when browsing locally because you can update your note hierarchies, theres less value for this in a published page when everything is already static

https://docs.dendron.so/notes/64f0e2d5-2c83-43df-9144-40f2c68935aa/ Must assume some knowledge that I don't have or I missed something in the requirements... but I thought https://github.com/dendronhq/dendron/issues/3654 must be trivial to fix. Probably update 4 strings in packges.json. So I went through the quick start and when I run yarn setup, I get this error: https://gist.github.com/jeep/544b0b5a01c5e5ed6d07850352567508 jeep@DESKTOP-JOE:~/dev/dendron$ node --version v16.17.1 jeep@DESKTOP-JOE:~/dev/dendron$ yarn --version 1.22.19 jeep@DESKTOP-JOE:~/dev/dendron$ lerna --version 5.6.2

Dendron Plugin Quickstart

After I Post a youtube video

The following error occurs: Application error: a client-side exception has occurred (see the browser console for more information).

Why did this happend?

The more I'm talking to people who use tools like Obsidian, the more I'm realizing multi-vault should prob be listed on pages such as https://wiki.dendron.so/notes/a84ff014-e871-445d-9366-d97f1ad882f1/ - people using other tools usually have to dance around with their own homemade solutions to multi-vault, not isolation on different systems (workplace, home, publishing, shared, private, etc.). And good luck trying to replicate an implementation anything like the vault dependency tree in other tools that Dendron can already handle for you. Continued multi-vault progress and support are honestly some of the biggest wins in my usage of Dendron.

i think you're right - its certainly a feature that carries with it a lot of complexity. might as well give ourselves credit for it 😅

ive been looking at quite a few documentation solutions lately. oh yes indeed lol. so i thought i would provide some learnings and internal values that i've developed in terms of what i expect out of a documentation frontend. firstly, i have learned to prioritize performance and bundle size. i think there are a lot of players who are okay at this, but I really believe svelte and astro to be above the ones that ship with a runtime like vueJS or react. astro strips away all the javascript, and svelte has no virtual dom its just a compiler. a snappy load time and experience is really important for users that I am targeting which may not have the best internet connection. next, i'm wondering if astro might be a good fit for dendron. if i get around to it with the time and figure out this HMR for the slug.filenames in the astro frontend, i'll be sure to publish a fork so others can use it. but i think astro might fit into dendron's "extend on any vertical" design tenet.

after refactoring a note the old filepath is still in the lookup menu. if this does not have an issue, let me know and I will create one. thanks!

i don't think it has an issue though we're tracking it internally (an instability with the sqlite migration). please submit an issue

https://github.com/dendronhq/dendron/issues/3713 🪴

Sould 'nav_order' entries be visible and editable in one place, for easy management?

Just wanted to say that I really like the note references feature. Even referencing certain sections works:

![[some.note#section]]

. Haven't looked into publishing yet, but read that you can even reference notes from private vaults without exposing the whole vault. Super useful.

Hi - after updating my mac to Ventura, I'm seeing the following error in vscode. Is there something I need to change? "Invalid Dendron Config [ { "code": "invalid_type", "expected": "boolean", "received": "string", "path": [ "publishing", "enableSiteLastModified" ], "message": "Expected boolean, received string" } ]"