@User @User Also on V2, I really like the graph display aesthetics - contrast and font especially - and I like the color change to green of a node when clicked to display its note. I see that clicking on the note title within the graph has no effect, clicking directly on the node dot is required to bring the note into view. I was wondering the reason for this, since for me it seemed intuitive to click the title. When I did and nothing happened I thought at first the note display feature wasn't working. I didn't try clicking the node dot until I went back to lookup the original graph documentation.

I agree that that's not the best UX - I'll take a note of that and take a look into it

I have been playing around with logseq [ https://logseq.com/ ] as well as Dendron. I like Dendron for the flexible hierarchy feature. Logseq also has an extremely compelling feature (for me) which is blocks and block queries. Basically, every press of the Enter key on the keyboard creates a new block. That block can then have properties and you can write queries that result in blocks that meet the query criteria. This is extremely powerful and flexible. Is there any chance that we can get this 'blocks' feature in Dendron? One workflow it unlocks for me is as follows: 1. At my day job as a manager, I spend many hours in meetings, during which I take notes. 2. In each meeting note, I can tag blocks with #person-name, #think, #poke, #waitfor, #read etc. as the meeting progresses 3. Then, I have pages in logseq which are results of {{query tag}} which contain all blocks with the queried tag. This is very useful to me because the next time I have a 1:1 with person-name, I just type {{query person-name}} and immediately see what I need to talk with that person about. If I have some time allocated to reading docs, I type {{query #read}} and immediately see the blocks with doc-names/links I need to read. 4. I tried this with Dendron but i) Tags seems less smooth than logseq ii) the only way to get to pages (not blocks) with the tags is through the backlinks window, which is small and off in a corner, making it difficult to read and process quickly. With logseq, I type {{query tag}} at the start of the doc and immediately see the blocks with that tag listed in the main document body, which is easy and smooth. The block level tagging and search also filters away other "noise" i.e. irrelevant-to-the-tag blocks that may be present in the meeting note(s).

I find Dendron great for longer, more permanent notes that may need to be referenced in the future. logseq is good for quick notes during meetings, whose contents may need to by dynamically queried later. Right now, I have a kludgy compromise by opening the Dendron workspace folder in logseq (which then scans Dendron notes and converts each bullet item in Dendron notes to a 'block' which can then be queried within logseq.). This gives the best of both worlds but is quite a kludge

Hello @here! Sorry for the late notice this week - we're still working on last week's issue, so we're going to try to pick a bunch that's a bit lighter this time around. Enough with the preamble, time to pick this week's CROP 🧑‍🌾 Hope you see something you like! 1. [Default Daily Journal note to vault](https://github.com/dendronhq/dendron/issues/820) 2. [Horizontal Split not working](https://github.com/dendronhq/dendron/issues/747) 3. [Option to fold frontmatter automatically](https://github.com/dendronhq/dendron/issues/489) To vote, respond with a 1️⃣ 2️⃣ or 3️⃣ to this message. voting closes tomorrow

It looks like the 1st option for the CROP makes it. It seems similar to this issue: https://github.com/dendronhq/dendron/issues/628 that I created a while ago. While the 1st option partly solves the issue it is less flexible and I still think choosing a vault is an useful approach

yes, I agree with @User that being prompted for the vault is more flexible

Unless there’s only one vault.

That's of course true but then I also don't see why we need to define a vault as target for daily notes?

we'll try to squeeze that in 0.47 as well 🙂

hey!! I'm getting some of my team this summer hooked on Dendron and I noticed that IMO, the homepage's "download" button is a bad CTA. What do you do after installing the VSCode extension, right? IMO it should instead be a page that lists the steps of downloading the vscode and then screenshots of running the proper command to initialize a workspace. I also think the "example instance" (wiki) should be featured more prominently since that's a great live example of what dendron's capable of. Maybe it should be a "get started" CTA button as well as a "demo"

yeah, your right. we're actually in the process of redesigning the home page so this is timely. 1. installation instructions instead of download: agreed. we can probably update this now 2. wiki example: you're right, we need a better way of showcasing it. we're working on announcing the seedbank later this month so we actually want to showcase a whole bunch of different workspaces on the homepage: https://wiki.dendron.so/notes/4039fc46-06b2-4f83-b817-fc490bafbcb3.html for now, maybe we'll just add a hero section with a link to the wiki 🤔

yeah, great feedback, we can link it to here: https://wiki.dendron.so/notes/d95b93bf-5e6f-4dd0-b7d7-c8e29e061876.html. Gimme a little bit to update.

Is this kind of what you meant @User ? https://dendron.webflow.io/

I changed the button to "Get Started" instead of download ... but, I think it flows. Thanks for intro'ing us to your teammates 🙂

Looks great. Also has a nice segue to the wiki as demo, since the getting started is in there

absolutely- and happy to put you in touch - I’m interning at Protocol Labs and the teams thinking quite a bit about knowledge management

Pushed to public 🙂 Thanks for calling this to our attention @User

glad to see !! keep up the awesome work

@User While I have you here, am wondering about your thoughts on this "feedback" 🙂

Is there any chance that we can get this 'blocks' feature in Dendron? > yes. its something we're looking at implementing. don't have a clear delivery date yet but probably before end of the year. the same goes for queries. Something we're also exploring is compatibility modes for Dendron and other tools (eg. you should be able to initialize dendron in logseq mode). This also doesn't have a delivery date atm 😅

Cool. By the way, if Dendron ends up supporting blocks and block queries, at least for my use case, I wouldn't need to use logseq any more 🙂 Right now, I am mixing both tools (opening Dendron folder in logseq) but that has its rough edges and may stop working the moment either Dendron or logseq changes something 🙂 Please let me know if I can help with this effort in any way. I can write user stories etc. to describe the needed feature.. am no coder, but can take a crack at it if someone provides a gentle introduction to getting started and mentors me while I'm at it.

actually, that would be great. we have a public rfc process. you can start with an issue and we can work with you to flesh it out into a rfc https://wiki.dendron.so/notes/f143ca38-dcc6-4cd3-b84b-997aec1160ef.html

@User thanks. I'll definitely submit an rfc. I feel comfortable writing a markdown file, but will need to figure out how to make a "pull request". Will review some of the existing RFCs and use the same format. Since you said, "yes. its something we're looking at implementing." in your original response, is there already an RFC on blocks and block queries that I can contribute to? Or should I start a new RFC for this?

no existing rfc yet but i think we have an issue in our backlog

Hello @here! It's that time of the week again 🙂 This week's CROP should have something for everyone. We're still working on a pretty major crop from a few weeks ago so we'd love your help in prioritizing a few quality of life improvements we had in our backlog 🧑‍🌾 Hope you see something you like! 1. [Position cursor to end of file when new note created](https://github.com/dendronhq/dendron/issues/800) 2. [Wipe cache command](https://github.com/dendronhq/dendron/issues/839) 3. [Vault Rename Command](https://github.com/dendronhq/dendron/issues/840) To vote, respond with a 1️⃣ 2️⃣ or 3️⃣ to this message. voting closes Sunday

@User we were able to squeeze in

lookupConfirm

issue for today's release 🙂

@User I had a look at the calendar widget just now. It's a bit of a mixed bag, but more usable then the new treeview. In a screenreader's browse mode, things work reasonably well. The table is a proper table, so table navigation commands work, and hitting enter on a cell that has content in it does open the correct note. So, I'd say this view is ...usable, but not pleasant to use, and here's why. - Cells that have content (i.e. are clickable because they have a note associated with them) are not semantically differentiated from the rest, making them hard to recognize as having a note associated, mostly because clicking any day in the calendar will just create a new journal note for that day. This is reasonably easy to fix with a bit of ARIA. - If you can currently arrow through the calendar (i.e. use the arrow keys to focus a particular day in the table) then this does not currently work with screenreaders. There are established patterns for fixing something like this though so this should be easy to fix if we do a bit of research. If this is not currently possible, it would help immensely if it were to be, as it makes sure people don't have to fall back to a screen reader's browse mode implementation. Finally a slight sidenote, currently the only way to get the calendar view to work is to enable the webUI which also enables the inaccessible treeview 🙂

If you navigate to another month in the new calendar view a new note is automatically created for the corresponding day, in that month i.e. if I view August today then 22nd August is created. Personally I'd like a way of viewing months (mainly for future planning) without immeadiately creating a note and being able to select a date for a new note. A today button would also be handy. Great start though.

Yeah thanks a lot!