Refactoring of embedded blocks from another note

[I-d-as]

Thanks @malecjan but it is not exactly that. Here are some differences that I don’t think are achieved with the combination of features you mentioned. I mean, broad strokes it is along the lines of and probably inspired by part of what you mentioned, but I believe the workflow would be completely unique and sandboxed from rest of vault.

@I-d-as

So technically, after this line linking occurred, you would be free to delete the source line or even the instance because it would be stored as an element of the note. Perhaps a list at the top of the note would contain these elements and act as a note explorer of sorts. And auto suggestions could work for adding it elsewhere within this and other lists while in the note.

(Only while in note with a definition list created in note with ability to drag drop instances)

@I-d-as

This definition list could allow list hierarchy adjustment in its own right; however, in this case you would only be moving it around for better organizational structure. Maybe it could have a flat mode toggle with sorting to quickly find what you are looking for. Although I know I have already gone too far, I would be remiss if I didn’t hint of a possibility these element instances may have taggability and back link capacity all restricted to the confines of the note. And this would logically provide an opportunity for an in-note search.

(The filtered note version to achieve definition list. Elements with ability to tag and achieve backlink functionality contained to within the note. Search limited to these special elements and tags contained to one note.)

Don’t get me wrong, I appreciate you looking over the idea and trying to summarize it, as unfortunately it definitely is a bit of a doozy.

@malecjan

maybe (to come) WYSIWYG in order to see tranclusions and edit at the same time.

(I don’t see editable transclusions being needed for what I envision but could make the editing process easier. I kind of thought clicking into the instances would bring you to the source element within definition list where edits would affect all instances. In practice, I do see the instances’ context being explained by separate list items folded within or above or adjacent to the instance.)

I may try to re edit my description in a new request so that there is a bit more clarity. Thanks for bringing this to my attention.