Let me start by saying I love the experience of Reflect. I came from Logseq, looking for something "simpler". Something with more "opinions" to help guide my process, instead of having to define it at each level. However, I do think that block level elements/references, etc. would go a long way in supporting the use of daily notes as a daily driver and provide another level of organizing and referencing note content in a way that is more discoverable.

Without block level elements, I feel like #tags have a diminished value. I almost feel that the intended process of Reflect (daily notes as the driver for most notes), is countered by the fact that this feature doesn't exist.

For example, my day consists mostly of meetings. Meetings about projects, with people, events, etc. Now, I have tagged notes for each project (#project), person (#person), and event (#event) that I can reference from my daily note. That works as expected. But when I go to either of those notes to see my backlinks (touch logs), I cannot get to a quick view of the "meeting" references. Because beyond meetings, I also reference these notes for other quick notes, touchpoints, etc.

Coming from Logseq, I would just use a #meeting tag on the parent block referencing whatever topic I'm focused on. But, in Reflect, all that does is make the daily note get pinged by a #meeting tag search and does not isolate the block (meeting) in which I called the tag. Not helpful IMO. While some meetings are recurring/routine, and I can create a dedicated meeting note, tag that one... Most of my meetings are not routine.

As I've seen others state... creating "nodes" (reference notes) for the categories of notes enabling a pseudo block reference that is easier to find in search/backlinks. But that just seems like a workaround and adds friction at capture. And forces me to create notes for "categories" that I feel should be "tags". (e.g., meetings, bizdev, profdev, resource, etc.) I'm creating empty notes to serve as nodes in my graph. Which IMO, indicates a category, best suited for a tag.

However, without a block level reference, using tags as categories in daily notes is just not useful. I've landed on not using Reflect tags within the daily notes, but that removes a great deal of value from tags as a means of organization/reference.

Any feedback on this request? I agree with a comment in the thread that block level references are table stakes.

"IMO this is table stakes requirement for a good PKM tool, particularly if you create longer form notes and/or dump long book excerpts or articles into the system. Technically you can tag the exact bullet point you want to mark for future reference but doing a search based on that tag (or even through AI query) will only surface that entire note which is highly inefficient as it then requires you to ctrl-F that tag to find that specific line. And if you have multiple instances of that tag this workaround is even less effective."

Considering a move here in the next 2-3 weeks as it's fairly annoying to not have that.

I hate that I have already put so much into this and still there is no word on whether or not this feature will end up in the product. Seriously considering if Reflect is worth keeping or if I should move to somthing else before I invest more of my time into it.

I cannot switch from Logseq without that feature.

Out of 744 items, this is number three, and only behind two that are currently being worked on, and get votes because they are visible in the kanban board.

Yet, this one is not under 'Planned', not 'Under review', and the Reflect team hasn't commented on it since it was posted two and a half years ago. If this is too difficult to implement, or if it is against the Reflect team's ethos, then why not at least communicate with your paying users who are spending time and energy providing valuable feedback?

If not block-level references, how about least giving headings a unique URI? That way we can create anchor links leading to a particular part of a note, saving a lot of time.

Please, at least speak to us on this subject.

IMO this is table stakes requirement for a good PKM tool, particularly if you create longer form notes and/or dump long book excerpts or articles into the system.

technically you can tag the exact bullet point you want to mark for future reference but doing a search based on that tag (or even through AI query) will only surface that entire note which is highly inefficient as it then requires you to ctrl-F that tag to find that specific line. And if you have multiple instances of that tag this workaround is even less effective.

Big plus on this one. I was just trying to find a quote from a kindle book I'd highlighted in my daily as it came to mind but the only way I could add this to my daily note for context was to write it again and tag the bog. a block-level reference would make this much much better

Yes, this should be prioritized

Has there been any input from the Reflect Team on this request? I've moved back to Obsidian for the time being because I found that not having this feature was very disruptive to how I take notes.

This is a MUST! This will also make the linked references much more useful if it shows the block and not the ENTIRE daily note. It makes the UI look clunky on one of the flagship features.