You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Obsidian works good with Atomic Highlights
Obsidian’s graph view visualizes the relationships between notes. Each highlight can act as a “node” in the graph, and by linking these highlights, users create a structured, interconnected map of ideas.
It aligns well with the Atomic Highlights approach.
I think it's easy to do.
Just create a separate file for each highlight. And reference it in the main file with the metadata.
example
fileTree:
omnivore
mainFile1
mainFile2
atomicFile
mainFile1
highLight1
highLight2
highLight3
mainFile2
highLight1
the content of mainFile1:
{{metaData}}
![[atomicFile/mainFile1/highLight1#^{{highlightID}}]]
![[atomicFile/mainFile1/highLight2#^{{highlightID}}]]
![[atomicFile/mainFile1/highLight3#^{{highlightID}}]]
the content of mainFile2:
{{metaData}}
![[atomicFile/mainFile2/highLight1#^{{highlightID}}]]
The text was updated successfully, but these errors were encountered:
Why
Obsidian works good with Atomic Highlights
Obsidian’s graph view visualizes the relationships between notes. Each highlight can act as a “node” in the graph, and by linking these highlights, users create a structured, interconnected map of ideas.
It aligns well with the Atomic Highlights approach.
I think it's easy to do.
Just create a separate file for each highlight. And reference it in the main file with the metadata.
example
fileTree:
the content of mainFile1:
{{metaData}}
![[atomicFile/mainFile1/highLight1#^{{highlightID}}]]
![[atomicFile/mainFile1/highLight2#^{{highlightID}}]]
![[atomicFile/mainFile1/highLight3#^{{highlightID}}]]
the content of mainFile2:
{{metaData}}
![[atomicFile/mainFile2/highLight1#^{{highlightID}}]]
The text was updated successfully, but these errors were encountered: