It kind of depends on what you want to use that “block” for. If you just want to be able to link to it, then a block reference like @Cooper is talking about is the way to go.
If on the other hand you want to group together information so that Dataview would be able to process it, then you’ll need to look into using lists/tasks. Or potentially wait until Datacore is released as is supposedly will have an extended view on paragraphs as block.
My preference for grouping information together is decorated tasks, that is tasks with unique status characters. These can be styled using CSS, and are readily available for access by Dataview. They’re also, due to their task nature, possible to use as backlinks from any queried result.
So I’ve assigned characters, or groups of tasks, to my interest groups like walking, training, telephone calls, visits, eating, costs, various hobbies, and so on. Each have their dedicated character, and I can then easily build my daily journals, and make whatever reports I want based upon tasks queries.
This is good question. It depends what metadata you want to associate to each paragraph. Block ids are just way to quickly navigate to specific content. In practice this can mean 1 paragraph or 5 paragraphs, depends how you want to interpret it. To associate several metadata to your paragraphs, you can use tags or properties in case you export your paragraphs to new notes. I recommend exporting your paragraphs because this requires one command only. After that you can add any metadata using note properties. In summary the “block” that you are looking for is new separate note.
In addition to Extract this heading context menu command there is Extract current selection context menu command. To configure extraction, go to Settings → Core plugins → Note composer, then press or
Great! I was on the verge of adapting my setup and had, in the past, used tasks in this way and felt like I must be misusing them. But, really they are very unique in what they are capable of, and hearing that you are doing this gives me a lot of confidence in, instead of going the direction I was going, trusting my instincts to leverage tasks this way.
I think, from my own experience, that this is likely an often overlooked or forgotten functionality. For me, it may have been because there is no link icon like with embeds. Or possibly, because Dataview provides the ability to interact with the task’s checkbox directly within query, it implies that the task itself within the query might be otherwise functionally disconnected, which it is not. To be clear for anyone unaware, what I believe @holroy is referring to is the ability to simply click (or tap) on the text of a task, which will behave as a link to the note containing the task, and will navigate the view to that area of the note with the task highlighted.
Amazing stuff! So glad you posted here. I would love to hear more about your system including but not limited to the use of unique status characters as well as css in relation to tasks and Dataview. Also, that’s great information about Datacore’s planned functionality with regards to paragraphs. Thanks so much!
I’ve posted some information in the thread below related to how to set it up. Basically I’m using that setup, and then I’ve chosen various characters to denote the various groups I’m interested in, like “disc golf”, “walking”, “work”, “food”, and various others. All groups or area of interests where I would like to keep some kind of tracking of those activities. I’m also using this to do bullet journaling tasks, that is tasks not only done or not done, but also partially started, migrated, cancelled, re-scheduled (or put on ice) tasks.
I’m considering doing another explanation of my usage of this concept, but I’ve not managed to allocate time to do so. Yet.